Fix multi-level pointer type tokenization in stackalloc and variable declarations #353
+75
−3
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.
The grammar only matched single
*for pointer types. Multi-level pointers (int**,int***) beyond the first level were incorrectly tokenized as arithmetic operators instead of type punctuation.Changes
array-creation-expression: Changed pointer suffix from(?:\s*\?\s*)?to(?:\s*\*\s*)*followed by(?:\s*\?\s*)?to support multiple pointer levels before nullable suffixlocal-variable-declaration: Changed(?:\s*[?*]\s*)?to separate pointer pattern(?:\s*\*\s*)*and nullable pattern(?:\s*\?\s*)?Example
All pointer asterisks now consistently receive
punctuation.separator.asterisk.csscope.Original prompt
stackallocfor pointer array declaration #319💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.