Span and friends may require work in Linq.Expression/DLR and dynamic binders

[VSadov]

It is not permitted to box these types and expressions/binders would need to know about that.

Otherwise there could be some relatively trivial ways to cause failures such as dynamically invoking a Span-returning method by name. That would easily result in a Span being boxed, which might fail very ungracefully.

[JonHanna]

Failing gracefully might at least be an improvement, if clearly not as good as just working.

I really must take a look at how Span works.

[karelz]

@VSadov only one area label please per issue - see Triage rules

[karelz]

cc @stephentoub who drives Span and friends work in CoreFX

[JonHanna]

@karelz probably best to put it on S.L.Expressions. That would be the first pin to knock down, as if we can't do anything with it in Expressions, then the other two can at best produce something that throws when it gets that far.

[karelz]

@JonHanna fine with me - it is the same experts/owners after all :)

[mattwarren]

I really must take a look at how Span works.

@JonHanna this blog post is a good place to start

[ViktorHofer]

@VSadov is the described situation still accurate or have improvements already been made to Span handling in Linq?

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.