Fred Silberberg
Fred Silberberg
This is triaged into the working set to accompany https://github.com/dotnet/csharplang/issues/7009.
> Essentially imagine an attribute named [BinaryCompatOnlyAttribute]. When a method is marked with this attribute then the compiler will never include it in a candidate set for purposes of overload...
> I'd say we should never remove those from the candidate set and prefer the ones with caller info because, as far as the compiler concerns, those are "more specific"...
@RikkiGibson `y` is `X`, because the input type is `X`, which has a `Deconstruct` method. It was deconstructed, the result was checked for `int` or `string`, then `y` was created...
Issues remain open until they are incorporated into the ecma specification. That's why it's labeled as such.
@jcouv for this to be an API proposal, we need to have an actual API shape proposed. @CyrusNajmabadi, I know you have an open PR with a draft: please make...
I like the idea of number two more, tbh. We could designate a subtable for connection info, and introduce a section in the spec that says clients must create/update a...
@AlekseyTs would be better to comment here.
However, I'm guessing this is intentional, as we don't emit `final` into the IL here.
### API Review * Naming of `Allows` vs `Allow`? * English prefers allows here * Shakespeare's famous question: "To By or not to By?" * For consistency with `ITypeSymbol.IsRefLikeType`, we'll...