> I don't believe that it even talks about scope affecting closures.

It doesn't need to because it's purely an optimization.

> We don't even know for sure what they're supposed to do, and if/when they're finally implemented, there's a high chance that we'll have used them incorrectly, so using them just increases the odds of breaking code later.

It says right there in the spec what it's supposed to do. When we see `scope` used in pull requests, we should verify that it's used correctly (that it doesn't escape the parameter, to the strictest degree, i.e. including indirections). Then if it breaks code when implemented, then that code was broken anyway, because we knew we intended the parameter to not be escaped.

The only good argument against using `scope` is if we suppose that it might get *removed*, but even then it's a trivial search & replace to fix broken code.