On 5 April 2012 21:32, Timon Gehr <timon.gehr@gmx.ch> wrote:
On 04/05/2012 08:05 PM, Andrei Alexandrescu wrote:
On 4/5/12 12:44 PM, deadalnix wrote:
Le 05/04/2012 19:35, Walter Bright a écrit :
On 4/5/2012 5:00 AM, Manu wrote:
C# and Java both have attributes, following these established design
patterns, I
don't think there should be any mystery over how they should be
implemented.

At the Lang.NEXT conference over the last 3 days, I was able to talk to
many smart people about attributes. But I did find some confusion - are
they best attached to the variable/function (i.e. "storage class"), or
attached to the type ("type constructor")? I think the former. Attaching
it to the type leads to all sorts of semantic issues.

>From your list of uses, it looks like attaching it to the variable or
function is an apropos solution.

They should be attached to declarations.

The question was whether the declaration affects the type of the
declared or not.

Andrei

Ideally it would be powerful enough to allow changing the type, but most applications probably want the type to stay the same.

Didn't someone already say there were existing language defined attributes that could be neatly implemented via libs if the feature were available? Which ones were they?