Yes,__traits did not stole my girl friend,but isn't better to name it trait? And I have thought I can find it in trait moudle but I was wrong.

Sam Hu wrote:
> Yes,__traits did not stole my girl friend,but isn't better to name it trait? And I have thought I can find it in trait moudle but I was wrong.

It's not in a module because it's a keyword.  You don't find "function" defined in any library.

As for being called __traits instead of traits, I suspect that's for at least one of two reasons:

1. so it won't invalidate existing code that uses the identifier "traits", and/or

2. because it's not something regular programmers should have to use; it should be used to build a higher-level API using templates.

Thank you so much for your help!

Just feel not so good that there are so many "__" in the code when making use of reflection from __traits.

Regards,
Sam

Daniel Keep:
> 2. because it's not something regular programmers should have to use; it should be used to build a higher-level API using templates.

Maybe Java programmers. D programmers need that functionality often.

Bye,
bearophile