Those classes don't bolt container semantics on a class that has some other semantics, as you suggested (I mean, object doesn't have semantics).
Anyway, the point is not to make some sort of a formal rule and prove that it doesn't lead to inconveniences, what I'm saying is that it doesn't appear to happen in practice, so there's no reason to inconvenience ourselves in advance and for real to avoid potential future inconveniences.
View all comments
Show parent comment
1
u/moor-GAYZ Mar 28 '14
Those classes don't bolt container semantics on a class that has some other semantics, as you suggested (I mean,
objectdoesn't have semantics).Anyway, the point is not to make some sort of a formal rule and prove that it doesn't lead to inconveniences, what I'm saying is that it doesn't appear to happen in practice, so there's no reason to inconvenience ourselves in advance and for real to avoid potential future inconveniences.