What went wrong in the code? What is the system trying to tell you?
This is a TDZ error. The system is trying to tell me that that x is in its TDZ when x = 2 is accessed, and is instead not available until let x is encountered in the scope.
What error message do you see?
v8: Uncaught ReferenceError: x is not defined
SpiderMonkey: ReferenceError: can't access lexical declaration `x' before initialization
Side note: Notice that SpiderMonkey's error message strangely surrounds x in a ` on one side and a ' on the other. Weird.
Which JavaScript environment produced this error?
v8 (in Chrome 70)
SpiderMonkey (in FF 65)
What error message would you like to see?
SpiderMonkey's error message is pretty good, much better than v8's.
But I would have worded it differently, and I would have included the "TDZ" terminology (instead of reusing the ReferenceError type) because that helps people google for this error.
TDZError: `x` cannot be accessed before its declaration
Using "initialization" in the error message is technically accurate, but it's not very helpful to the user because they likely don't understand the nuance of the fact that a let / const have been "hoisted" for the scope but not initialized. I teach that detail in my workshops, but the vast majority of devs don't understand that.
My error message shifts attention to describing the problem accurately without an unnecessary detail to distract.
If you're going to keep ReferenceError as the error class, the message should read:
ReferenceError: `x` cannot be accessed in its TDZ before its declaration
Do you agree to license your suggested error message under an MIT-style license?
What is the code triggering the message?
What went wrong in the code? What is the system trying to tell you?
This is a TDZ error. The system is trying to tell me that that
xis in its TDZ whenx = 2is accessed, and is instead not available untillet xis encountered in the scope.What error message do you see?
Uncaught ReferenceError: x is not definedReferenceError: can't access lexical declaration `x' before initializationSide note: Notice that SpiderMonkey's error message strangely surrounds
xin a`on one side and a'on the other. Weird.Which JavaScript environment produced this error?
What error message would you like to see?
SpiderMonkey's error message is pretty good, much better than v8's.
But I would have worded it differently, and I would have included the "TDZ" terminology (instead of reusing the
ReferenceErrortype) because that helps people google for this error.Using "initialization" in the error message is technically accurate, but it's not very helpful to the user because they likely don't understand the nuance of the fact that a
let/consthave been "hoisted" for the scope but not initialized. I teach that detail in my workshops, but the vast majority of devs don't understand that.My error message shifts attention to describing the problem accurately without an unnecessary detail to distract.
If you're going to keep
ReferenceErroras the error class, the message should read:Do you agree to license your suggested error message under an MIT-style license?
Yes