Implements compile time warning for datum[] #397
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lummox recently made this a RUNTIME error, but also irrrespective of that this tends to mask HELL vars[] security holes. We really should be linting for it. I had to implmenet operator overloading support for the builtin parser, which was far more annoying then I expected. Bit scuffed, but it works. (I am unsure of how to parse for "" though so I left that unimplemented) This will likely throw errors on most codebases, I'm unsure of how to handle that..
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lummox recently made this a RUNTIME error, but also irrrespective of that this tends to mask HELL vars[] security holes. We really should be linting for it.
I had to implmenet operator overloading support for the builtin parser, which was far more annoying then I expected. Bit scuffed, but it works. (I am unsure of how to parse for "" though so I left that unimplemented)
This will likely throw errors on most codebases, I'm unsure of how to handle that..