4 ms·
> Dealing with singular values can be very useful, but not everything is a value. Some things are fundamentally “non-values” e.g. instructions/control-flow/decl
by lmm 6y ago
> Dealing with singular values can be very useful, but not everything is a value. Some things are fundamentally “non-values” e.g. instructions/control-flow/declarations.
If there are important things in your language that aren't values, that's a problem in your language. You really don't need any non-values; just look at, say, Haskell.
> As I have described above, both the OOP and OS both share similarities:
> Traditional-OOP: A (linear) value hierarchy of behaviour. The values act as agents.
> Ownership Semantics: A (linear) value hierarchy of responsibility. Agents are responsible for values.
This is just bollocks once you actually look at the details of it. An inheritance hierarchy is fixed once and for all at compile time, and can't ever change; either there's no way to change which class a given class inherits from at all, or at best there's some uncontrolled dark magic you can do. Whereas a defining characteristic of ownership semantics is that ownership can be safely passed from one owner to another in a controlled way.