Skip to content

Restore parsing from old branch#81705

Merged
333fred merged 4 commits intodotnet:features/dictionary-expressionsfrom
333fred:parsing
Jan 5, 2026
Merged

Restore parsing from old branch#81705
333fred merged 4 commits intodotnet:features/dictionary-expressionsfrom
333fred:parsing

Conversation

@333fred
Copy link
Member

@333fred 333fred commented Dec 16, 2025

Restore the parsing from the previous dictionary expressions branch and update tests. Binding is not yet restored.

Relates to test plan #81860

Restore the parsing from the previous dictionary expressions branch and update tests. Binding is not yet restored.
@dotnet-policy-service dotnet-policy-service bot added the Needs API Review Needs to be reviewed by the API review council label Dec 16, 2025
@CyrusNajmabadi
Copy link
Contributor

I will look tomorrow. Pretty sure I wrote it. But it will be good to do a once over again.

@333fred 333fred marked this pull request as ready for review December 16, 2025 18:01
@333fred 333fred requested review from a team as code owners December 16, 2025 18:01
@333fred
Copy link
Member Author

333fred commented Dec 16, 2025

@CyrusNajmabadi @jcouv for reviews.

analyzer.VerifyAnalyzeSymbolCalledForAllSymbolKinds();
analyzer.VerifyAnalyzeNodeCalledForAllSyntaxKinds([]);
// PROTOTYPE: Add to all-in-one
analyzer.VerifyAnalyzeNodeCalledForAllSyntaxKinds([SyntaxKind.KeyValuePairElement]);
Copy link
Contributor

@CyrusNajmabadi CyrusNajmabadi Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: i've found it easier to jsut add to all-in-one. there's already a collection section at the bottom of the file. #ByDesign

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no binding behavior, so I don't want to deal with that yet.

Copy link
Member

@jcouv jcouv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks (commit 3)

@333fred 333fred enabled auto-merge (squash) January 5, 2026 19:46
var colonToken = this.TryEatToken(SyntaxKind.ColonToken);
return colonToken != null
? _syntaxFactory.KeyValuePairElement(expression, colonToken, this.ParseExpressionCore())
: _syntaxFactory.ExpressionElement(expression);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Entirely up to you. But verbiage was added to the spec stating that we take a lexical prefix oriented view around parsing. We could link to that, or include that text here. Or, if you think it's not necessary, that's also fine.

@CyrusNajmabadi
Copy link
Contributor

LGTM.

@333fred 333fred merged commit 4082a58 into dotnet:features/dictionary-expressions Jan 5, 2026
28 of 29 checks passed
@333fred 333fred deleted the parsing branch January 5, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants