remove the "cute" error messages

[rakyll]

fmt.Printf("ouchie, solve error: %s", err)

Go tools have a specific tone and style (simple comprehensive and precise), hence we don't see them return errors in such an unlikely style. Follow the Go tool conventions, please. This is a candidate to be an official tool.

[sdboyer]

Oh, of course. The places where we don't follow that convention, like the one you've cited, exist more or less because it gives the clear indication that it's an area that is unfinished. There's no way we'd let them into the final tool. (let's not forget - pre-alpha!)

[rakyll]

I can sign up to fix these as I see.

It is good to align with the Go project as soon as possible to making the blessing of this tool or reusing of its code easier if succeeds. It'd be a shame if we had to re-rewrite this tool.

[sdboyer]

I can sign up to fix these as I see.

🎉 🎉

so long as there's a clear TODO (or equivalent) left behind, i'm all 👍 to that.

It is good to align with the Go project as soon as possible to making the blessing of this tool or reusing of its code easier if succeeds. It'd be a shame if we had to re-rewrite this tool.

for sure. and, like i noted elsewhere (too many issues flying around right now), this is something that just gets harder as time goes on.

tbh, i'm less concerned about that for this tool than i am for gps. i've put a lot more deliberate effort into it than the parts of dep i've written (which has generally been written with a more experiment/prototyping mindset). still, though, there's likely plenty of style/convention things that i've missed, because i haven't spent the time acculturating to how core reviewers do things.

[sdboyer]

i think these are pretty much gone now - closing