http://d.puremagic.com/issues/show_bug.cgi?id=4427


Manu <turkeyman@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |turkeyman@gmail.com


--- Comment #10 from Manu <turkeyman@gmail.com> 2012-11-24 14:49:05 PST ---
(In reply to comment #9)
> > Many of these could easily be turned into templates
> 
> The is ==struct and __traits are not really intended to be user-facing. They are intended to be embedded into templates which then can present a simple, straightforward user interface.
> 
> Sometimes those templates do need to work hard internally to get the information, but being able to is all that's relevant.

Well with this in mind, perhaps we can complete the suite of std.traits? There are a lot missing. I'd certainly like to clean up that aspect of my code before I depart, as it's the most confusing and unreadable section by far. Particularly for new-comers who haven't taken the time to wrangle those sorts of problems yet (who I will be leaving it to) :/

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

http://d.puremagic.com/issues/show_bug.cgi?id=4427


Andrej Mitrovic <andrej.mitrovich@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrej.mitrovich@gmail.com


--- Comment #11 from Andrej Mitrovic <andrej.mitrovich@gmail.com> 2013-01-09 14:30:51 PST ---
I've lost track here, what's left to implement that requires the compiler's help by exposing a new __trait?

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

http://d.puremagic.com/issues/show_bug.cgi?id=4427



--- Comment #12 from Manu <turkeyman@gmail.com> 2013-01-12 03:18:49 PST ---
(In reply to comment #11)
> I've lost track here, what's left to implement that requires the compiler's help by exposing a new __trait?

I think the __trait's were more or less good now (at least for me personally), and Kenji had a bug/task where he was fleshing out std.traits. I'm not sure where that landed. I copied his example/prototype code locally and used that, not sure if it was ever completed/merged/documented.

Sorry, I've been a major advocate for this stuff, and I'm currently AWOL. Back in 2-3 more weeks and I'll start making noise again ;)

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

http://d.puremagic.com/issues/show_bug.cgi?id=4427



--- Comment #13 from Andrej Mitrovic <andrej.mitrovich@gmail.com> 2013-01-12 11:54:22 PST ---
Jonathan can you give us an updated on what's still missing?

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

http://d.puremagic.com/issues/show_bug.cgi?id=4427



--- Comment #14 from Rob T <alanb@ucora.com> 2013-03-29 00:06:50 PDT ---
(In reply to comment #13)

I would like to see something like isNullable(T) that evaluates to true if the type value can be assigned a null.

Eg,

struct S { ... }
S* s;
class C { ... }

isNullable( S ) is false
isNullable( typeof(s) ) is true
isNullable( C ) is true

--rt

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------