On Wednesday, 16 October 2013 at 19:19:26 UTC, Jacob Carlborg
wrote:
On 2013-10-16 21:08, simendsjo wrote:
Remove all would probably be more in sync with getAttributes
that
returns all attributes, but removing only the first would
allow greater
flexibility. It's easy to remove all if you have a way to
remove one,
but the other way around isn't as easy :)
How would you remove all? I guess something like this:
!@(foo, foo)
But how can that be generalized? Unless we get a trait for
removing attributes.
Yes, sorry. I was thinking about a new __trait and running a loop.
Is this when we should be dreaming of the all-powerful AST macros
again?
