meetings/working-groups/roles/extension-wg-2024-06-21.md
See description in https://github.com/dotnet/roslyn/pull/74012
We'll have follow-up issue for nullability of the extra parameter.
We'll have follow-up issue for capturing the receiver when it is a type parameter.
Note: When implementing interfaces, a modopt(ExtensionAttribute) could be brought into the picture and cause a conflict/ambiguity.
Many sections of the spec need to consider the kind of type. Consider a few examples:
P?[A]B
considers whether P is a nullable value type. So it will need to handle the case
where P is an instance of an extension type on a nullable value type,It may be possible to address all those cases without changing each such section of the spec, but rather by adding general rules ("an extension on a class type is considered a class type" or some such).
explicit extension E<T> for T { void M(); } new C().M(); new S().M();