Open hellerve opened 5 years ago
The compiler now cathes this error properly.
Or actually only the first one is caught (missed that there were a second one). So this will have to be fixed still...
I think the second one requires the fixes I'm working on in the sets-of-lifetimes
branch.
maybe data structures like Array should be able to take ownership (or have ownership automatically transferred to it when it has a reference to a variable that goes out of scope and would otherwise be deallocated) ?
Currently, references can be invalidated by invalidating their origin inside their scope.
It is also possible to set references to point to values in a more short-lived scope:
Both of these can be prevented by checking the origin of a reference and whether the origin scope still exists; an error could be emitted if it doesn’t.
Cheers