madelson

@trullock I haven't looked at the parser code, but maybe some logic like this could work? * Try to parse the sequence starting with `(` as an argument list; if...

Will this fix be backported to .NET 6?

@MihaZupan thanks for following up. We've deployed the workaround and are actively monitoring. The error was transient, so we want to wait a week or so before declaring victory.

@MihaZupan I still have to do some more digging to confirm early next week, but so far it looks like the workaround **may not** have fixed the issue for us.

@MihaZupan ok I think we have a false alarm; the error was in an environment that hadn't received the fix yet. I'll continue to monitor. Here's what our implementation of...

EDIT: thought we had a conclusion here but still looking.

I'd be interested in working on this @buyaa-n . We'd need to decide on the behavior, though. Should we treat `T&` as a "scalar" type like we do `Nullable` or...

@buyaa-n / @terrajobst any update on this? I'm hesitant to start working on it without a clear spec of the intended behavior. It would be nice to start from @smdn...

> If we treat them as compound type and put their nullability info in info.ElementType what would the info.ReadState infor.WriteState would express? I agree that this would be confusing, since...

> Therefore, I think it is better to treat it as a compound type Here's the case I would make for scalar type: **Compat**: today, you can check the nullability...