Simple @tagged attribute for unions [OT]
Andrew Wiley
debio264 at gmail.com
Fri Nov 19 16:10:44 PST 2010
On Fri, Nov 19, 2010 at 5:46 PM, Bruno Medeiros
<brunodomedeiros+spam at com.gmail> wrote:
> On 22/10/2010 04:04, Andrei Alexandrescu wrote:
>
>> On 10/21/2010 08:41 PM, bearophile wrote:
>>
>>> I have suggested yet another attribute, @tagged:
>>> http://d.puremagic.com/issues/show_bug.cgi?id=5097
>>>
>>> Bye, bearophile
>>>
>>
>> And almost exactly six hours ago:
>>
>> On the other hand, currently there are many D2 features that are
>>> unfinished and buggy, so adding even more stuff is not a good idea.
>>> And I think named arguments are a purely additive change. So Walter
>>> may add them later when the current features are implemented well
>>> enough. Currently it's much more important to focus on eventually
>>> needed non-additive changes instead.
>>>
>>
>> Hope you agree with yourself :o).
>>
>>
>> Andrei
>>
>
> How did I miss that! It's bearophile's best comment ever! :D
This isn't really related but it's an idea that I randomly had while reading
that bug report:
What if functionality like this could be implemented in mixins rather than
compiler-defined annotations? The idea would be that an annotation, when
applied to something, would be "instantiated" in some form, allowing it to
mixin code somehow. I know that's vague, but it seems like it would have
powerful applications for things like ORM libraries and other libraries.
On the other hand, annotations go from metadata to something that
potentially changes the code you're writing, which may not be a good idea.
Disclaimer: This is utterly random and you're free to tell me it's
foolishness.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20101119/43f36ecf/attachment.html>
More information about the Digitalmars-d
mailing list