BCS wrote:
That's why I'd still require types to be marked as serializeable by
the programmer.
How would you do that aside from mixins?
Make the user implement a marker interface, or let him provide a
(single) special class member which fulfill the same function, or
introduce annotations
Hello grauzone,
BCS wrote:
That's why I'd still require types to be marked as serializeable by
the programmer.
How would you do that aside from mixins?
Make the user implement a marker interface,
that would work (for classes) but IMHO the side effects of that are more
invasive and it
BCS wrote:
introduce annotations into the language.
NO, not an option.
What, why? Sure, this is not a realistic option.
Well, I can switch the default but, in my experience, most of the time
repetition doesn't matter. I also dissagree on the relatively useless
Oh really?
optimization
Hello grauzone,
BCS wrote:
introduce annotations into the language.
NO, not an option.
What, why? Sure, this is not a realistic option.
D1 is fixed, and D2 will be in the next few months. I'm not going to even
think of targeting D3 at this point. I'm writing this to be used, not as
a
