Charles Stoner

> Are all of these changes necessary in order to successfully compile? Yes, these are changes needed to compile successfully. These are typically methods that have a `ref` parameter and...

If `RuntimeFeatures.NumericIntPtr` is not found, it looks like the compiler will treat a type reference to `System.IntPtr` as `System.IntPtr` unless there is an associated `[NativeInteger]` attribute.

@ericstj, there is no API currently for indicating that `System.IntPtr` should be considered equivalent to `nint`, assuming that is the goal. One consideration is that such an API would affect...

> public void ReadOnlyIndexer_RefLikeStructParameter_02(LanguageVersion languageVersion) Consider testing this without `unsafe` as well since it looks like the original test didn't depend on unsafe code. (I realize the tests above also...

See also https://github.com/dotnet/roslyn/issues/62327.

> > Control cannot leave the block other than after the trailing expression unless an exception is thrown executing the statements or the expression. > Is this for ease of...

Thanks @julealgon. That example was from an earlier iteration of the proposal. I've corrected the example in https://github.com/dotnet/csharplang/pull/4728.

From [lambda-improvements.md](https://github.com/dotnet/csharplang/blob/main/proposals/csharp-10.0/lambda-improvements.md#natural-function-type): > _Function_types_ are used in a few specific contexts only: > - implicit and explicit conversions > - method type inference ([§11.6.3](https://github.com/dotnet/csharpstandard/blob/draft-v6/standard/expressions.md#1163-type-inference)) and best common type ([§11.6.3.15](https://github.com/dotnet/csharpstandard/blob/draft-v6/standard/expressions.md#116315-finding-the-best-common-type-of-a-set-of-expressions)) >...

If we synthesize a parameterless constructor whenever a `struct` contains field initializers, we'd need to synthesize a parameterless constructor that calls the primary constructor for `record struct` types because the...

Decision from LDM today: Never synthesize a parameterless constructor for `struct` types; report an error if a `struct` type declaration includes field initializers but no explicit constructors. _Notes are forthcoming._