> It starts from a marketing position of "Safety With No Compromises" Since such a tradeoff is not possible (full safety for free?!) I doubt there's any such m

> It starts from a marketing position of "Safety With No Compromises" Since such a tradeoff is not possible (full safety for free?!) I doubt there's any such marketing. > The world is filled with very reasonably compromised memory-safe runtimes that are excellent choices for your new system. Bringing a whole managed runtime just to handle a single structure with cycles in your program is not reasonable. There's no problem with using a simple GC for a tiny part of an otherwise manually managed program just how there's no issue in managing memory manually for a small, but performance sensitive part of your GC managed program.