On 2014-05-05 15:32, Jonathan M Davis via Digitalmars-d wrote:
Maybe they should still be
visible for the purposes of reflection or some other case where seeing the
symbols would be useful
Yes, it's useful for .tupleof to access private members.
--
/Jacob Carlborg
On Monday, 5 May 2014 at 13:33:13 UTC, Jonathan M Davis via
Digitalmars-d wrote:
IIRC, it had something to do with member functions, but I'd
have to go digging
through the newsgroup archives for the details. In general
though, I think
that private symbols should be ignored by everything outside
On Mon, 05 May 2014 13:11:29 +
Dicebot via Digitalmars-d wrote:
> On Monday, 5 May 2014 at 12:48:11 UTC, Jonathan M Davis via
> Digitalmars-d wrote:
> > On Mon, 05 May 2014 15:55:13 +0400
> > Dmitry Olshansky via Digitalmars-d
> > wrote:
> >> Why the heck should internal symbols conflict wit
On Monday, 5 May 2014 at 12:48:11 UTC, Jonathan M Davis via
Digitalmars-d wrote:
On Mon, 05 May 2014 15:55:13 +0400
Dmitry Olshansky via Digitalmars-d
wrote:
Why the heck should internal symbols conflict with public from
other
modules? No idea.
Because no one has been able to convince Walte
On Mon, 05 May 2014 15:55:13 +0400
Dmitry Olshansky via Digitalmars-d wrote:
> Why the heck should internal symbols conflict with public from other
> modules? No idea.
Because no one has been able to convince Walter that it's a bad idea for
private symbols to be visible. Instead, we've kept the C
05-May-2014 12:03, John Chapman пишет:
Importing both core.thread and std.regex results in a conflict as both
define a Thread type.
Perhaps the regex module's author assumed there'd be no clash since it's
a template - Thread(DataIndex). Should I file a bug suggesting a name
change? Or maybe D ou
Importing both core.thread and std.regex results in a conflict as
both define a Thread type.
Perhaps the regex module's author assumed there'd be no clash
since it's a template - Thread(DataIndex). Should I file a bug
suggesting a name change? Or maybe D ought to allow both
parameterised and
