Future of SafeRefCounted

[Derek Fawcus]

On Tuesday, 25 February 2025 at 11:46:44 UTC, Dukc wrote:
> If you don't recall, and if I understand it correctly DIP25 is 
> essentially DIP1000 limited only to `ref` and `return ref`. 
> `scope`/`return scope` rules for 
> pointers/slices/classes/struct/unions aren't included. It's 
> already the default in the current language.

How does this compare with a similar mechanism in C#, which seems 
to have something akin to scoped pointers?

See the postscript in the below article, where this was added as 
a means of working around limits in C#'s existing "borrow 
checking", and preventing escapes.

https://em-tg.github.io/csborrow/

That brought to mind this discussion, and hence wondering if 
there are any answers there to be "stolen", since to my ignorant 
first glance it seems similar to what D is groping towards with 
DIP 1000.