September 11, 2019Re: DIP 1021--Argument Ownership and Function Calls--Community Review Round 1
Posted in reply to Mike Franklin
On Wednesday, 11 September 2019 at 09:37:38 UTC, Mike Franklin wrote: > [snip] > > I recently discovered a programming language called "Pony" (https://www.ponylang.io/) and I believe it has an interesting take on the pointer aliasing problem that is quite different than Rust and is more akin to how D addresses such problems (e.g. through attribution). > > Pony uses what they call "Reference Capabilities" to tell the compiler how references can or cannot be aliased, and I think it is relevant to the same problem that this DIP and other efforts within D are trying to solve. > > You can find more information here: > https://tutorial.ponylang.io/reference-capabilities > https://zartstrom.github.io/pony/2016/08/28/reference-capabilities-in-pony.html > https://www.youtube.com/watch?v=HGDSnOZaU7Y&t=1869s > > I hope you find it interesting if not influential. > > Mike I was under the impression that some early Rust work was similar to Pony before they switched things up. I think the reference capability that is most relevant to D is the iso one. That lines up with Oliver Faure's scheme to add a unique qualifier  I think. https://email@example.com
September 15, 2019Re: DIP 1021--Argument Ownership and Function Calls--Community Review Round 1
Posted in reply to Mike Parker
Ownership/lifetime is definitely a very useful feature for D. However, what is purposed by this DIP seems to be very limited. I wonder how useful this will actually be in practice. (That been said, since we could easily iteratively improve on top of this DIP, this is not really a problem). It would be nice if this DIP could include some real world bugs that would have been caught by this form of ownership/lifetime analysis.
Copyright © 1999-2018 by the D Language Foundation