5 ms·
I think Rust attempted to do a much more conservative version of this (same language, different sigils on pointers depending on whether pointers were refcounted
by geofft 12y ago
I think Rust attempted to do a much more conservative version of this (same language, different sigils on pointers depending on whether pointers were refcounted or ownership-transferred) and determined that it didn't work in practice. Libraries have to use one scheme or the other, nobody made APIs that exposed both schemes, and calling between them was too much of a hurdle. So in practice people ended up settling on a single pointer type, which was -- somewhat surprisingly for the language designers -- the non-refcounted one. And the language got rid of syntax for the refcounted one, and everything became more usable.
I could believe that with more money and resources everything would have been rosy, but my understanding of the facts doesn't particularly support this.