On Wednesday, 2 November 2016 at 19:49:24 UTC, Jacob Carlborg
wrote:
On 2016-11-02 17:30, Márcio Martins wrote:
Can we get a getMember and a getOverloads that won't check for
visibility or anything else?
__traits appears really powerful, but every-time I try to use
it for
anything other than a
On 2016-11-02 17:30, Márcio Martins wrote:
Can we get a getMember and a getOverloads that won't check for
visibility or anything else?
__traits appears really powerful, but every-time I try to use it for
anything other than a toy example or very simple serialization, it seems
like everything fal
On Wednesday, November 02, 2016 16:30:04 Márcio Martins via Digitalmars-d
wrote:
> Can we get a getMember and a getOverloads that won't check for
> visibility or anything else?
That's coming. There was a big discussion on it after the import rules were
changed. But IIRC, it was decided that we wo
Can we get a getMember and a getOverloads that won't check for
visibility or anything else?
__traits appears really powerful, but every-time I try to use it
for anything other than a toy example or very simple
serialization, it seems like everything falls apart due to some
detail... and I end
On Saturday 16 October 2010 17:03:51 Tomek Sowiński wrote:
> What's the status quo on member functions defined outside the type?
>
> import std.array;
>
> void main() {
> int[] arr = [1,2];
>
> // compiles, should it?
> int a = __traits(getMember, arr
Tomek Sowiński napisał:
> What's the status quo on member functions defined outside the type?
>
> import std.array;
>
> void main() {
> int[] arr = [1,2];
>
> // compiles, should it?
> int a = __traits(getMember, arr, "front");
>
&
What's the status quo on member functions defined outside the type?
import std.array;
void main() {
int[] arr = [1,2];
// compiles, should it?
int a = __traits(getMember, arr, "front");
// compiles (called popFront), should it?
__traits(getMember,
