This seems rather lofty.
Are you planning on being platform agnostic?
How are you going to make a tool that is supportive on so many languages?

My best guess is using IDE plugins is the best way to go about it.

Then Go for vscode plugin.

@rootshell
Just shooting the breeze with this idea, obviously there are more nuances, language differences, ect. But the basic premise is using the error message to round up a few possible related causes from the source & some solutions. That can solve the error.

If I am not wrong that is similar to a Linter.

@canonbolt
There are tons of carbon copy apps these days. Especially if the app is closed source, and missing ideal features that would otherwise be implemented if not for developer laziness, or not part of the app's scope or vision. I mean how many remakes, rehashes and renditions of the same old movie, or video game we've seen and played a 1000 times, do we need made? The people churning them out seem to have a valid reason in their heads for going about it; like it or not. Why leave it all up to the so called "originators"?

@adempus
And besides, theres always room for improvement somewhere. If improvement is rejected, then you show em how it's done 😛

@adempus any particular ide or writer app u wanna develop this? Coz i was also thinking on similar lines for sublime text 2.0.2.

@Fede26 only for runtime exceptions
there's a difference between runtime and compile-time, and there's a difference between errors and exceptions