In most places, handling exceptions just prints a stack trace. Shouldn't error handling do more? Like explain to user what went wrong and how to fix it? Something else?
This is a general problem in the code, not a single bug in some specific place. Maybe contributors could select some specific places for themselves to fix in this respect? Like a certain class and error handling there. Or something.
In most places, handling exceptions just prints a stack trace. Shouldn't error handling do more? Like explain to user what went wrong and how to fix it? Something else?
This is a general problem in the code, not a single bug in some specific place. Maybe contributors could select some specific places for themselves to fix in this respect? Like a certain class and error handling there. Or something.