We have loud, annoying errors for unexpected and unsupported expressions. This helps us keep up-to-date with upcoming and bleeding edge JavaScript features and is a nice forcing function to make sure we're doing so well. (as an aside: Historically, the incentive for most reporters is unfortunately to "make the error go away" rather than scanning the new expression thoroughly and well, but that just means we need to apply more scrutiny to those cases and make sure there are great tests for these features).
What I noticed though, is that we don't have a test to ensure that a WontEverExistfantasyExpression will always throw an error. We should do that and I think it could be an easy bug for an outside contributor.
mozfreddyb
commented
2 years ago
We have loud, annoying errors for unexpected and unsupported expressions. This helps us keep up-to-date with upcoming and bleeding edge JavaScript features and is a nice forcing function to make sure we're doing so well. (as an aside: Historically, the incentive for most reporters is unfortunately to "make the error go away" rather than scanning the new expression thoroughly and well, but that just means we need to apply more scrutiny to those cases and make sure there are great tests for these features).
What I noticed though, is that we don't have a test to ensure that a
WontEverExistfantasyExpressionwill always throw an error. We should do that and I think it could be an easy bug for an outside contributor.