[Issue 13773] std.traits.ReturnType does not resolve inout

2019-12-20 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13773

berni44  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||bugzi...@d-ecke.de
 Resolution|--- |INVALID

--


[Issue 13773] std.traits.ReturnType does not resolve inout

2014-11-25 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13773

Martin Nowak c...@dawg.eu changed:

   What|Removed |Added

   Priority|P1  |P2
   Severity|enhancement |normal

--


[Issue 13773] std.traits.ReturnType does not resolve inout

2014-11-25 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13773

--- Comment #1 from Kenji Hara k.hara...@gmail.com ---
I think this should be marked as invalid or changed as a compiler enhancement,
because:

1. ReturnType takes an alias (through the index 0 of the TupleParameter).

2. Currently alias parameter cannot handle the runtime context of the
expression,
  so ReturnType!(m.keys), ReturnType!(c.keys), and ReturnType!(i.keys) are 
  perfectly same with ReturnType!(Foo.keys).

3. The return type of Foo.keys is inout(int)[].

--