Destructors or multi-platform `Closeable`/`Disposa...

# language-proposals

[Dominaezzz]

Destructors or multi-platform `Closeable`/`Disposable` interface.
Just to provide some standard way of specifying resources to be released by the user and not necessarily the runtime.
A class/object with a destructor would pretty much behave like a class that implements AutoCloseable, which I think should be the JVM implementation of it.

[Dominaezzz]

Also, I realize that 'Destructor' may not be the appropriate term for what I describe.

[Andreas Sinz]

can you give us a pseudo-code example of how it should work?

[Dominaezzz]

class Texture(path: String) {
    val texId: Int

    init {
        texId = glGenTexture()
        // Read from file.....
    }

    deinit {
        glDestroyTexture(texId)
    }
}

val sprite = Texture("res/image.png")
// use image in game.
free sprite

[spand]

You might want to create an issue or try #stdlib

[Andreas Sinz]

@Dominaezzz and when should this deinit be called?

[Dominaezzz]

Whenever the user doesn't need the object anymore.

[Dominaezzz]

GC doesn't have be involved.

[diesieben07]

Why is this better than a Closeable interface?

[spand]

I think he just wants AutoCloseable in common code

[Dominaezzz]

It's not. I was proposing a multi-platform version. Closeable is only available on the JVM back-end.

[diesieben07]

Your code above used some new keywords and language constructors, that's why I was confused.

[diesieben07]

A common AutoCloseable is a good idea.