Repository navigation
Checker: change more than 1000 possibilities in match range to notice - #19862
Merged
Merged
Conversation
Member
|
I wonder why is this even there. |
Contributor
Author
|
why does |
Contributor
Author
Member
spytheman
approved these changes
Nov 14, 2023
This file contains hidden or 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
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.
because it is not user's fault but compiler's. it shouldn't be an error with
-prod🤖 Generated by Copilot at e6eca41
Changed the warning level and wording of a match range message in
vlib/v/checker/match.vto better inform the user about the compile time impact of large ranges.🤖 Generated by Copilot at e6eca41