Champion "Span<T>, aka interior pointer, aka stackonly struct" (C# 7.2)

[gafter]

• Proposal added
• Discussed in LDM (2016-11-01)
• Decision in LDM
• Finalized (done, rejected, inactive)
• Spec'ed

/cc @jaredpar @VSadov @jcouv

[gafter]

A draft of more precise span safety rules is at https://gist.github.com/gafter/20aee8cfac801caebd19b49af180f708

[gulshan]

The proposal link is broken.

[initram]

@gulshan The correct link is https://github.com/dotnet/csharplang/blob/master/proposals/csharp-7.2/span-safety.md

The proposal was moved to the csharp-7.2 folder

[jcouv]

Fixed link. Thanks @initram

[Nukepayload2]

Are ref structs CLS-Compliant? The following code is legal in Visual Studio 15.7.2, but StackOnlyType obviously depends on a c#-only language feature.

using System;
[assembly:CLSCompliant(true)]
namespace MyLibrary
{
    [CLSCompliant(true)]
    [Obsolete("Types with embedded references are not supported in this version of your compiler.", false)]
    public ref struct StackOnlyType
    {
    }
}

[tarikguney]

Not sure if this topic is active and any C# designer pays attention to this but I have asked about the reason why ref struct are the chosen keywords rather than something else like stackonly struct, here and https://softwareengineering.stackexchange.com/questions/398954/why-did-c-choose-ref-for-ref-struct

And I even liked stackalloc struct suggested by Eric Lippert better. Could we get some explanation, please?