On Monday, 16 January 2017 at 19:45:33 UTC, Jonathan M Davis
wrote:
I can see that as an argument not to add something that it's in
std.traits to __traits or why something should be added to
std.traits rather than __traits, but if something already
exists with __traits, why duplicate that logic in std.traits?
It seems like it complicates std.traits for no benefit as well
as risking having the behavior of __traits and std.traits
differ, which could cause confusion and bugs.
- Jonathan M Davis
Why? Because working with introspection in D requires constantly
switching between at least 4 different documentation pages to
find the introspection you're interested in.
