[Proposal]: Breaking change warnings
@MadsTorgersen is already working on this.
Since Dec 12, 2024.
- Dominant language
- C#
- Stars
- 12.7k
- Forks
- 1.1k
- Avg merge
- 11h 1m
- Merged PRs (30d)
- 3
Description
Breaking change warnings
- Specification: https://github.com/dotnet/csharplang/blob/main/proposals/breaking-change-warnings.md
- Discussion: https://github.com/dotnet/csharplang/discussions/8864
Summary
Allow very limited breaking changes in C# when this enables significantly simpler feature designs that are easier to learn, understand and use.
Retroactively add warnings in previous language versions to help identify and fix user code that would be vulnerable to such breaks upon a language version upgrade.
Design meetings
https://github.com/dotnet/csharplang/blob/main/meetings/2023/LDM-2023-10-16.md#breaking-change-warnings
https://github.com/dotnet/csharplang/blob/main/meetings/2024/LDM-2024-02-07.md#breaking-change-warnings
https://github.com/dotnet/csharplang/blob/main/meetings/2024/LDM-2024-03-04.md#breaking-changes-making-field-and-value-contextual-keywords
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.