Usability of "allMembers and derivedMembers traits now only return visible symbols"

[Ethan Watson via Digitalmars-d]

On Wednesday, 31 August 2016 at 09:25:52 UTC, Basile B. wrote:
> nice idea, but this doesn't change the fact that the traits 
> that access the results of the "omniscient" allMember must be 
> tweaked to access everything.

I'm okay with this. My PrivacyLevel workaround does exactly this 
in fact.

But I would like to be able to read (and write) all members of a 
class without needing to mixin a template and without having to 
resort to .tupleof. Use case here is the extensive struct use we 
have, if we want them to match C++ exactly then that's where 
mixins become potentially hairy.