On 5/12/2025 4:16 AM, Manu wrote: > `scope` has nothing to do with @safe, and it MUST work in its own right, > otherwise the code is lying to the author, and it's an effective liability. An escape hatch is always needed. For example, you might want to interface with a 3rd party library that is scope-correct, but is not annotated with `scope`.