But I'm already running with the idea that all slices are "borrowed", so we could say the same thing about pointers, if you have one, assume it is borrowed and you shouldn't store it nor free it.
I think we could do the whole owned pointer concept in D too, by
making a struct with a disabled copy constructor. I don't know
much about Rust's specifics though so not sure if that's an exact
match.
- Rust moving away from GC into reference counting Paulo Pinto
- Re: Rust moving away from GC into reference counting Dicebot
- Re: Rust moving away from GC into reference countin... Adam D. Ruppe
- Re: Rust moving away from GC into reference cou... Dicebot
- Re: Rust moving away from GC into reference... Adam D. Ruppe
- Re: Rust moving away from GC into refe... Dicebot
- Re: Rust moving away from GC into refe... H. S. Teoh
- Re: Rust moving away from GC into refe... Rob T
- Re: Rust moving away from GC into ... Brad Anderson
- Re: Rust moving away from GC into ... Kagamin
- Re: Rust moving away from GC i... Brad Anderson
- Re: Rust moving away from GC into reference counting Manu
- Re: Rust moving away from GC into reference counting Paulo Pinto
