Idea: Ownership & lifetime escape analysis by variables in reference to

[Ola Fosheim Grøstad]

On Sunday, 29 May 2022 at 09:21:16 UTC, rikki cattermole wrote:
> Worse of all, you end up missing all of the things @safe can 
> actually catch.

Yes, and that is why the idea of a simple solution doesn't work. 
I seldom make mistakes in functions without loops.

@safe is most valuable in functions that are "complicated" 
(containing loops or other intricacies).

Some overhead in @safe is ok, because most applications don't 
need to be faster than Java in 95% of the code. So if you make 
95% @safe then you only need to be careful with the remaining 5%.

Which is kinda how it works with C now, people write C libraries 
and use those with high level languages. But it is more 
convenient with one unified language (and that could make D 
attractive for Linux GUI applications).