In summary, you want to move GC/reference counting to be debug only feature, with compiler putting in the proper disposes based on when owned ref gets out of scope?
I would love to be with the new hotness: prove everything at compile time (debug runtime?) - no GC languages. But it does come at a writing complexity. I want to solve the problem at hand not baby the compiler to put in the proper frees where they supposed to be. I don’t want to solve owned puzzles with cryptic errors. I just want to get stuff done. I like that you can write nim like python without thinking about crap, then come back and make things faster. If the error messages can guide you to a better faster GC-less language I am all for it. I think the hard part is in the error messages for this feature not the feature itself. I personally have no major issue with current GC. Having the ability to do most of the stuff on the stack is a huge win over other heap-only languages.
