What if the error was more descriptive out of the box? Unless of course the goal is to just compete with C++ error reporting.

The goal is to probably avoid duplicating efforts when llvm-symbolize already exists.

There’s obviously a snarky comment to make here about Go developers and duplicating efforts.

If I follow the advice

https://pastebin.com/8M9Dbrgj

Not sure how that's any better... I still have no idea that the error occurred on line 2