C++ pattern matching is coming

[rikki cattermole]

On 25/10/2022 8:12 AM, Paul Backus wrote:
> 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.

Right now I'm building up my library infrastructure using @safe and DIP1000.

@live on a memory object sounds very attractive to ensuring memory owned 
in a data structure/nullable ext. stays alive and won't be deallocated.

But not on a function, that asks far too much of people, so I'm 100% in 
agreement with Paul over this.