fix incorrect slicing by length detection cases #22344
Merged
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.
I initially just wanted to simplify the code that handles the slicing syntax in AstGen.zig but then found two bugs related to the special Slicing By Length syntax:
This example will incorrectly trigger slicing by length even though no end index has been provided. It will crash the compiler.
In this example, the provided sentinel expression is never analyzed and no sentinel mismatch safety check is reported.
The PR that added the slicing by length special case has explicitly mentioned support for
s[start..:sentinel][0..len]ands[start..:sentinal_1][0..len:sentinel_2]but appears to have never tested what happens if the first sentinel is invalid.The diff as a whole is not very readable. I would recommend to look at the commits individually.
Here is a Benchmark of running ast-check on Sema.zig: