# Swift mention in C++ safety post

**URL:** <https://forums.swift.org/t/swift-mention-in-c-safety-post/76091>\
**Category:** Compiler\
**Tags:** memory-safety, optimizations\
**Created:** [November 18, 2024, 12:51pm UTC](https://forums.swift.org/t/swift-mention-in-c-safety-post/76091 "2024-11-18T12:51:58Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\
**Post date:** [May 9, 2026, 4:02am UTC](https://forums.swift.org/t/swift-mention-in-c-safety-post/76091/6 "2026-05-09T04:02:33Z")

</div>

Just watched [this talk on the new Cangjie programming language from Huawei](https://youtu.be/ujpl5_TmAaE), where the speaker mentions Swift's reference-counting when explaining that they use a concurrent GC instead (edit: a better [talk about Cangjie from PLDI 2025](https://youtu.be/VoC-tlcBXH0)). An interesting green-field effort for the Swift team to look at, including the highlighted intro of effects handlers.

Also found [this year-old blog post about zig's `comptime` meta-programming](https://matklad.github.io/2025/04/19/things-zig-comptime-wont-do.html) interesting, especially given [ongoing work on Swift's approach](https://forums.swift.org/t/pitch-literal-expressions/85505).

---

_[View the full topic](https://forums.swift.org/t/swift-mention-in-c-safety-post/76091)._