@NicolasRinaudo@functional.cafe
Post #1063180
2026-04-02 19:56 UTC
I’ve been fielding questions on capture checking and have reached the conclusion that the documentation forces you to think about them a certain way, and that’s the wrong mental model.
It’s unfortunate that they’re so tied to capabilities in their vocabulary when they solve a different, orthogonal problem. One that is useful for capabilities, certainly, but distinct from them.
Replies (1)
-
@NicolasRinaudo@functional.cafe 2026-04-02 19:58
The mental model that works for me starts from: we’re simply trying to prevent some variables from escaping their intended scope. That’s it. The way this happens is clever and sometimes a little convoluted, but it’s *not* to do with capabilities. It just so happens that we don’t want capabilities to escape their intended scope. But there are other such things.