This is a general discussion issue to get some conversation on the topic, not an error message itself.
I am wondering how we would define a good error message. I have a couple of ideas:
relationship to the source code - a good error message would clearly show its relationship to the source code as it was written.
Error in relation to intended code - sometimes it is hard to tell exactly what the programmers intent was, but the closer the error message is to the intention, the more useful it is.
suggestions on how to fix - maybe we can give tips on where the problem is likely coming from?
Those are some initial thoughts. Let me know what you folks think.
Do you agree to license your suggested error message under an MIT-style license?
This is a general discussion issue to get some conversation on the topic, not an error message itself.
I am wondering how we would define a good error message. I have a couple of ideas:
relationship to the source code - a good error message would clearly show its relationship to the source code as it was written.
Error in relation to intended code - sometimes it is hard to tell exactly what the programmers intent was, but the closer the error message is to the intention, the more useful it is.
suggestions on how to fix - maybe we can give tips on where the problem is likely coming from?
Those are some initial thoughts. Let me know what you folks think.
Do you agree to license your suggested error message under an MIT-style license?
Yes