C++ pattern matching is coming

[Walter Bright]

On 10/24/2022 12:12 PM, Paul Backus wrote:
> The problem with using @live and @safe together is that (a) you cannot *safely* 
> call a @live function from a non- at live function, or vice-versa (because 
> non- at live functions will not honor the above rules), and (b) as a consequence, 
> changing a function from @safe to @safe @live is a breaking API change.
> 
> This means that existing @safe D projects will not be able to adopt @live, and 
> the community will have to build an entirely new @safe @live ecosystem from the 
> ground up in order to see any benefit in practice. The more likely outcome is 
> that D users will stick with their existing @safe codebases (which they've 
> invested time and money in) and ignore @live altogether.

@live does indeed allow for incremental, function by function use of @live. This 
is inevitable as using an ownership/borrowing system requires restructuring the 
algorithms and data structures.