Controlled Memory Management

[sirinath]

Is it possible to have have a way to specify quasi C++ style delete but a more safer way. Basically Grizzly (https://grizzly.java.net/) style memory management in the context of general memory management if you would have another crude analogy.

You can specify if a particular object and any containing objects to n level can be collected if they are not live.

Also ability to mark a class or individual fields on whether they escape or not and perhaps make this a compile time constraints.

Also some of the constraints currently in Lancet can be compile time checks than just JIT time checking.

Also is it possible to more to a more friendly license sooner than later.

[sirinath]

Also objects with reference constraints. E.g. can only be stored in local variables, fields cannot be returned or passed to other objects, etc. this will help stack allocation.