search

WillSullivan / idownvotedbecause

I downvoted because...
http://idownvotedbecau.se
MIT License
265 stars 66 forks source link

Full exception info may be excessive #47

Open treeowl opened 6 years ago

treeowl commented 6 years ago

With some languages, environments, and examples, exceptions can get very long. They may get too long to fit in an SO question (dozens or hundreds of pages), but even if they fit, they may be too big for anyone to want to look at. I think the page on missing exception info should provide some tips for dealing with this situation.

WillSullivan commented 6 years ago

That's fine. I haven't had to deal with that, nor do I venture in tags where this might be an issue (I suppose, since I've never encountered that problem before with a question), so if anybody has some tips please feel free to add!

treeowl commented 6 years ago

You're more likely to encounter very long stack traces in functional languages, where recursion is more likely to be deep. But I was actually thinking about the sorts of error messages the Glasgow Haskell Compiler produces when it is compiled in compiler-debugging mode (not the way users normally compile it!) and it encounters "core lint" errors (indicating violations of internal invariants in the optimizer). These messages can be quite absurdly long because they try to expose the full IR the compiler was processing when it ran into trouble. Of course, most SO questions aren't about debugging industrial-strength compilers....

On Mon, Dec 18, 2017 at 11:01 AM, Will Sullivan notifications@github.com wrote:

That's fine. I haven't had to deal with that, nor do I venture in tags where this might be an issue (I suppose, since I've never encountered that problem before with a question), so if anybody has some tips please feel free to add!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/WillSullivan/idownvotedbecause/issues/47#issuecomment-352470555, or mute the thread https://github.com/notifications/unsubscribe-auth/ABzi_VK__UU4ALvJ9aWcutbXJak4BdQPks5tBoxXgaJpZM4RE6U3 .

sehe commented 6 years ago

@treeowl have a look at some c++ compiler messages :) Seriously, there's rarely any reason to abbreviate even those. In fact, one can print messages from multiple compilers or link to an online IDE where the compiler can be easily switched/run side-by-side.

I'd simply keep the wording "complete information" because 99% of the time, "too much" doesn't exist nor hurt.

LindaLawton commented 6 years ago

does this qualify or to much info or could it be expanded?