Safe and efficient C++ interoperability via non-escapable types and lifetimes

The recent Swift updates add increasingly niche and theoretical features that are of questionable practical use.<p>Meanwhile the compiler still can&#x27;t compile many even mildly complex SwiftUI views and expressions with the &quot;The compiler is unable to type-check this expression in reasonable time&quot; error.<p>It does not even tell you what part of code it is having issues with so you could change it. You have to comment&#x2F;uncomment blocks of code to find the problematic part.

Apple wants to migrate away from C++, including code in the kernel, so they need a safe, low-overhead language.<p>Swift has originally been designed as an ObjC replacement, mostly for UI glue code, with conveniences more like a scripting language.<p>So now they&#x27;re working on making Swift support more low-level low-overhead code.<p><a href="https:&#x2F;&#x2F;youtu.be&#x2F;lgivCGdmFrw" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;lgivCGdmFrw</a>

Looks very similar to C#&#x27;s `ref struct` (<a href="https:&#x2F;&#x2F;learn.microsoft.com&#x2F;en-us&#x2F;dotnet&#x2F;csharp&#x2F;language-reference&#x2F;builtin-types&#x2F;ref-struct" rel="nofollow">https:&#x2F;&#x2F;learn.microsoft.com&#x2F;en-us&#x2F;dotnet&#x2F;csharp&#x2F;language-ref...</a>).

I sometimes feel that my own lifetime is a type of non-escapable.

My wild fantasy of a MacOS-native fork of UNetbootin (C++) has just become closer to reality.