Show warnings when FOR variable cannot exceed TO limit #297
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.
e.g.
for i as ubyte = 0 to 255This seems to come up occasionally (e.g. https://freebasic.net/forum/viewtopic.php?f=3&t=29304), so I thought it might be worth having a warning for.
I'm quite rusty on compiler internals, and I fully expect that this can be approved upon, but sometimes it's perhaps easier to start by proposing something and seeing how it can be improved, than just to throw out a suggestion and add it to a mental Todo list somewhere.
It covers upper and lower limits for all the integer types, and I've started a warning test that should hit all the cases.