Neal Gafter
Neal Gafter
This was discussed in the 2017-10-02 LDM meeting, with the following tentative directions: - We will try to get ref reassignment into release 7.2 - The syntax for ref reassignment...
A tentative spec for ref local reassignment is here: https://github.com/dotnet/csharplang/pull/963
This was further discussed in the 2017-10-25 LDM meeting, where it was requested that the following be added to the scope of this championed issue for tentative work in C#...
Under your suggestion, the ref assignment equivalent of `M(a = b)` for a ref parameter would be `M(ref ref a = ref b)` and a similar issue arises for chained...
> The second `ref` on the left is obviously redundant and could be elided. No, the first `ref` distinguishes whether we’re calling a method that receives a value versus one...
@alrz I think `params Span` would be inherently dangerous. Just using such an API inside a loop would likely cause stack overflow. That makes me doubt we'd add it as...
On second thought, we could reuse the same Span for the same call point in the code in subsequent iterations of the loop.
@axel-habermaier cast the switch expression to `object` to work around this issue.
I have added a proposal for this, and a PR exists for it in the Roslyn repo at https://github.com/dotnet/roslyn/pull/18784.