Steve

@kayoub5 It turns out that the NativeAOT toolchain doesn't care about the library name at all. So let's keep using `wpcap` as the default library name.

Should the name be `YieldAsync` to follow the naming convention around async here?

Just to note that allowing overload priority could open a can of worms and shouldn't be rushed out to the public. I would instead recommend making `OverloadResolutionPriorityAttribute` an internal type...

Does this also apply to extension methods? I think yes as the attribute applies on any method. Assuming we already have: ```cs class C1 { public void M(int[] a) =>...

> Do you have any concerns not addressed by the proposal? Nope. I'm okay with it as long as the overload priority only affects the resolution of overloads which are...

Implicit conversion from strings to `ROS` should be disallowed for `params ROS`. See https://github.com/dotnet/csharplang/discussions/8172

I think some part of this proposal needs to be updated with https://github.com/dotnet/csharplang/pull/7994 which makes using `Span`, `ReadOnlySpan` as the underlying type a thing in async code as well.

How about reusing the existing dictionary syntax? Given that we already have ```cs var dict = new Dictionary { [key] = value } ``` We can somehow use a similar...

Apparently the current metadata is blocking us to have an efficient implementation of all those kinds of modern features. Another approach would be introducing metadata v3.0 to provide all the...

BTW I would like to expect we can have a native MapControl just like what the UWP MapControl was, instead of the current WebView based garbage.