Here’s the thing: “no locks” and “no allocations” exist because there are scenarios in which use of locks or allocations is bad and avoiding them is good. Nobody has articulated any situation in which using operations implemented with unsafe primitives is bad and avoiding them is good. It’s like having a function color for @usesEvenNumberOfCPUInstructions—sure, that’s a property you could theoretically enforce, but what’s the point?
2 Likes