# New function colour: unsafe

**URL:** <https://forums.swift.org/t/new-function-colour-unsafe/65408>\
**Category:** Discussion\
**Tags:** memory-safety, unsafe\
**Created:** [June 7, 2023, 7:43pm UTC](https://forums.swift.org/t/new-function-colour-unsafe/65408 "2023-06-07T19:43:51Z")\
**Posts on this page:** 1\
**Showing post:** 100

<div class="post-metadata">

**Author:** ![beccadax](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/beccadax/32/34217_2.png) [@beccadax](https://forums.swift.org/u/beccadax)\
**Post date:** [June 21, 2023, 11:06pm UTC](https://forums.swift.org/t/new-function-colour-unsafe/65408/100 "2023-06-21T23:06:32Z")

</div>

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?

---

_[View the full topic](https://forums.swift.org/t/new-function-colour-unsafe/65408)._
