Since ref struct is stack-only, it could have a destructor, which would be executed when the struct goes out of scope. If I write a function library for others, although I provide dispose function, users can still ignore it and forget to release resources. I can't force them to use "using". But if ref struct supports destructor, I can use it to wrap my functions to ensure releasing resources.

[SamiG42]

    Since ref struct is stack-only, it could have a destructor, which would be executed when the struct goes out of scope. If I write a function library for others, although I provide dispose function, users can still ignore it and forget to release resources. I can't force them to use "using". But if ref struct supports destructor, I can use it to wrap my functions to ensure releasing resources.

For example:

ref struct A
{
    FileStream file;
    public A(string filename)
    {
        file = new FileStream(filename, FileMode.Open);
    }
    ......  //other member functions
    ~A() //destructor 
    {
        if(file)
        {
           file.Close();
           file=null;
        }
    }
}

static void test()
{
    A a=new A("D:\test.txt");
    ......
} //destructor of "a" would be executed here automatically

related issue: #231

---

Add a rule: ref struct with destructor can't assign each other.

Originally posted by @ygc369 in #1110