Skip to content

Update breaking change doc#82071

Merged
CyrusNajmabadi merged 1 commit intodotnet:features/collection-expression-argumentsfrom
CyrusNajmabadi:lastLastPrototype
Jan 18, 2026
Merged

Update breaking change doc#82071
CyrusNajmabadi merged 1 commit intodotnet:features/collection-expression-argumentsfrom
CyrusNajmabadi:lastLastPrototype

Conversation

@CyrusNajmabadi
Copy link
Contributor

@CyrusNajmabadi CyrusNajmabadi commented Jan 18, 2026

Relates to test plan #80613

@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner January 18, 2026 18:57
@CyrusNajmabadi CyrusNajmabadi merged commit f0d9217 into dotnet:features/collection-expression-arguments Jan 18, 2026
3 of 4 checks passed
@CyrusNajmabadi CyrusNajmabadi deleted the lastLastPrototype branch January 18, 2026 19:37
***Introduced in Visual Studio 2026 version 18.4***

`with(...)` when used as an element in a collection expression, and when the LangVersion is set to PROTOTYPE, is bound as arguments passed to constructor or
`with(...)` when used as an element in a collection expression, and when the LangVersion is set to 'Preview', is bound as arguments passed to constructor or
Copy link
Member

Choose a reason for hiding this comment

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

@RikkiGibson We lack a mechanism to track and update this location when the new language version is added... I'm not sure what to do here.

Copy link
Member

Choose a reason for hiding this comment

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

Seems like we could afford to predict the future here and just write 15.0 here. Or something like "when the LangVersion is set to '15.0' (or 'Preview' until that's available), ..."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i agree. we should just mention the next version. If we're wrong, c'est la vie. We can update it. The breaking changes doc would be a clear place to look when teh version is solidified.

Copy link
Member

Choose a reason for hiding this comment

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

Fixed in #82099

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.

4 participants