3 ms·
But what will happen once there are "value objects" in the language? Will the new libraries be needed? Will the existing ones get some new genericity?
by acqq 13y ago
But what will happen once there are "value objects" in the language? Will the new libraries be needed? Will the existing ones get some new genericity?
- taeric 13y agoHmm.... good point. I would assume that would be a different initiative. Though, my initial thought of "value types" getting boxed doesn't really make sense. What would they even be boxed as?
- acqq 13y agoThe article writes: "Wrapping. Just as the eight primitive types have wrapper types that extend Object, value types should always have both an unboxed and a boxed representation. The unboxed representation should be used where practical; the boxed representation may be required for interoperability with APIs that require reference types. Unlike the existing primitive wrappers, the boxed representation should be automatically generated from the description of the value type." So there is some boxing planned. What does it mean for the programmers, the users of existing libraries? Ah, I believe gordaco hints to that in his comment.
- taeric 13y agoRight, but does that mean I'll have to write the boxed and unboxed representation? If not, how do you distinguish between boxed and not? edit: And yes, I see it says they will be auto generated. It is the "how to distinguish" question that is non-obvious to me.