An interesting presentation. After watching it, I found myself wanting some sort of list of questions to answer about a data type you are about to code that would tell you whether you should think of it as a value or an object. I guess something like a decision tree. I realize the decision is not that simple but it might be a good starting point nonetheless.
A list a questions would be useful - that's a great idea. Typically I "just know" which I want (and typically it is values), but there are probably times it is less clear. I think the slide with Objects vs Values and their properties (ie at 1:14:32) might be a start.
@@tvaneerd After thinking about it a little more, I guess I also "just know" but fear that there are edge cases where I go with object but could have gone with value and made the code simpler and more reliable. Figuring out how to identify those edge cases is perhaps what it is really about.
What's the problem? The answer to the "Ship of Theseus" question is right there in the question. The ship of Theseus is obviously the ship that belongs to Theseus. If Theseus chooses to replace parts and throw the old parts away then clearly he still owns a ship, that is the ship of Theseus. If someone else collects the reject parts and builds them up into a ship that is clearly not the ship of Theseus, that is the ship of whoever's name. This train of thought seems to be all about ownership and lifetimes. Correct handling of ownership and lifetimes is one of the many reasons I have stopped using C++ and moved to Rust.
Great talk Tony!
An interesting presentation. After watching it, I found myself wanting some sort of list of questions to answer about a data type you are about to code that would tell you whether you should think of it as a value or an object. I guess something like a decision tree. I realize the decision is not that simple but it might be a good starting point nonetheless.
A list a questions would be useful - that's a great idea.
Typically I "just know" which I want (and typically it is values), but there are probably times it is less clear.
I think the slide with Objects vs Values and their properties (ie at 1:14:32) might be a start.
@@tvaneerd After thinking about it a little more, I guess I also "just know" but fear that there are edge cases where I go with object but could have gone with value and made the code simpler and more reliable. Figuring out how to identify those edge cases is perhaps what it is really about.
What's the problem? The answer to the "Ship of Theseus" question is right there in the question. The ship of Theseus is obviously the ship that belongs to Theseus. If Theseus chooses to replace parts and throw the old parts away then clearly he still owns a ship, that is the ship of Theseus. If someone else collects the reject parts and builds them up into a ship that is clearly not the ship of Theseus, that is the ship of whoever's name. This train of thought seems to be all about ownership and lifetimes. Correct handling of ownership and lifetimes is one of the many reasons I have stopped using C++ and moved to Rust.
mycolouredcircle = colour{other}
I'm still getting trouble to find a good 3d point able to work seamless in cartesian and polar coordinates and being a struct.
using Point3D = variant;
😂
Fabulous! But what about Rust?!!