You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this SO question, I took a look at the JavaScript runtime to see if buildParseTrees is defined for a parser. Indeed it is, but I noticed there is one applied occurrence of the field erroneously spelled _buildParseTrees. Of course, in the warped world of JS, this is not caught either by compiler or runtime.
Also, there is no "getBuildParseTree()" noted here and here.
I realize "code reviews" are old school, but relying on a terrible programming language like Javascript to find errors is not going to work.
The text was updated successfully, but these errors were encountered:
Ideally the runtime would / should be written in TypeScript (or at least type-checked JavaScript annotated with JSDoc types), which would catch these immediately at build time. JavaScript is only a "terrible programming language" if the tools one is using for it are terrible.
In this SO question, I took a look at the JavaScript runtime to see if
buildParseTrees
is defined for a parser. Indeed it is, but I noticed there is one applied occurrence of the field erroneously spelled _buildParseTrees. Of course, in the warped world of JS, this is not caught either by compiler or runtime.Also, there is no "getBuildParseTree()" noted here and here.
I realize "code reviews" are old school, but relying on a terrible programming language like Javascript to find errors is not going to work.
The text was updated successfully, but these errors were encountered: