The .NET 11 analysis was verified against Preview 7 and re-verified against release candidate 1. Both
produced identical results, with one exception that has not converged.
Re-run the probe against the final release and confirm:
- Whether runtime async is enabled by default without
<Features>runtime-async=on</Features>.
Microsoft documentation says it is; neither Preview 7 nor release candidate 1 behaves that way.
This is the single finding that could still move, and it governs the priority of the runtime
async work.
- Whether the C# 15 constructs still compile to the shapes recorded in the analysis: a union as a
sealed struct implementing IUnion with [UnionAttribute], a closed hierarchy as an abstract
class with [IsClosedTypeAttribute], and extension indexers using the <G>$ and <M>$ marker
type layout.
- Whether async iterators and
async void methods still use classic state machines.
- Whether
<UseRuntimeAsync> is implemented in the final SDK. It is absent from the release
candidate 1 SDK entirely.
Analysis: Documentation/DotNet11-CSharp15-Impact.md in postsharp/PostSharp.
— Claude for Gael
The .NET 11 analysis was verified against Preview 7 and re-verified against release candidate 1. Both
produced identical results, with one exception that has not converged.
Re-run the probe against the final release and confirm:
<Features>runtime-async=on</Features>.Microsoft documentation says it is; neither Preview 7 nor release candidate 1 behaves that way.
This is the single finding that could still move, and it governs the priority of the runtime
async work.
sealed struct implementing
IUnionwith[UnionAttribute], a closed hierarchy as an abstractclass with
[IsClosedTypeAttribute], and extension indexers using the<G>$and<M>$markertype layout.
async voidmethods still use classic state machines.<UseRuntimeAsync>is implemented in the final SDK. It is absent from the releasecandidate 1 SDK entirely.
Analysis:
Documentation/DotNet11-CSharp15-Impact.mdinpostsharp/PostSharp.— Claude for Gael