right, but assume the language can assign either semantic to any particular pass.
Conversation
How does the language know which the caller means?
2
it *decides* which the caller means. Like I said, identity is hand-waved away. Aside from that it’s optimization.
1
*squiiiiiiint* I don't see how you can hand wave identity away
1
1
pretend it’s by magic up to and possibly including the elimination of state.
1
(for example, you could limit it to any pure type)
1
Okay, so for any immutable type, yes, this makes sense.
2
Now, let’s define all types as being immutable by default. Like, you have to get out a wrench to make it mutable.
1
I get it, but I think we're talking about a very different language now. One of the appeals of Swift is its approachability… :/
3
1
But even without this, I think struct/class & the stack makes Swift *less* approachable, not *more*.
4
3
Replying to
I'd argue less approachable for new people (simply due to more concepts), more approachable for ObjC coders.
3
who are as able to learn new semantics as anyone. And there are (over time) more of the former group anyway.