On Tuesday, 27 May 2014 at 16:47:38 UTC, Etienne wrote:
You're right, it's obviously easier to keep it as the same pointer syntax but hijack the stdlib malloc functions to forcibly go through the GC.
That is an option, and having a hijacked malloc would probably also make it possible to optimize out uneccessary allocations as well as inline allocations.
If you have a GC-pointer type and ban transitions to regular pointers unless they are borrowed pointers then that would also be ok (you don't need to hijack malloc then).
