I think the fact that Task closures don't require explicit self is a huge footgun :(

Helge Heß

@helge@mastodon.social

Having closures w/o a GC is the real footgun 🏃‍♀️

December 11, 2025 at 9:17:05 PM

Explicit self is just one special case that doesn’t deserve an own solution. The problem affects any capture, as each capture might also refer to self or produce other cycles.
I think what you really want is explicit capture lists, not explicit self in the body. (the { [self, a, b] in … } thing)

Elk Logo

Elk is in Preview!

Thanks for your interest in trying out Elk, our work-in-progress Mastodon web client!

Expect some bugs and missing features here and there. we are working hard on the development and improving it over time.

Elk is Open Source. If you'd like to help with testing, giving feedback, or contributing, reach out to us on GitHub and get involved.

To boost development, you can sponsor the Team through GitHub Sponsors. We hope you enjoy Elk!

三咲智子 Kevin DengAnthony FuPatakDaniel Roe

The Elk Team