[throwaway894345]

> I personally value greater chances of correctness at compile time way more than development speed

In my experience, I don’t get much additional correctness for the extra effort, but rather I get independence from the GC, which is worth much less to me.

If we’re optimizing for correctness alone, I think development times could improve significantly by swapping the borrow checker for a gc. I know the borrow checker aids in correctness beyond what a gc does, but IMO the returns diminish rapidly. And I’m not sure how well this would work in practice, but maybe you could keep the borrow checker and add a GC, with every reference type being gc<> by default (not sure if that would recoup any of the extra correctness that a borrow-checker affords or not).

[OvermindDL1]

Things like the borrower checker helps manage all resources, a GC only manages memory.

[OvermindDL1]

Or rather RAII, borrow checker is a different feature that is not related to garbage collection

[throwaway894345]

Yes, I understand. To quote myself:

> I know the borrow checker aids in correctness beyond what a gc does