• Denton Cockburn <diboss hotmail.com> Dec 01 2007

Denton Cockburn <diboss hotmail.com> writes:

4tuu4k002 sneakemail.com Wrote:

 
 Hi
 
 This is the monthly status for the unofficial d wish list: 
 http://all-technology.com/eigenpolls/dwishlist/
 
 Right now the wish list looks like this:
 
 146  Reflection API (#6)
 142  Stack tracing (#26)
 103  vectorization (#10)
 77  Multiple return values (tuples (#28)
 75  Multiple opCast per class (#24)
 68  Short syntax for new (#18)
 63  extra compiler values (#19)
 63  Debug check for null reference (#52)
 62  unit test after compilation (#1)
 62  Native AMD64 codegen (#36)
 58  !in (#44)
 51  Explicit out/inout (#38)
 48  Return-type overloading (#49)
 47  Unit test isolation  (#2)
 43  Posix threads support native (#3)
 42  Array masking (#11)
 42  Foreach on first/on last (#42)
 39  better syntax for cast (#23)
 35  Explicit type initializers (#35)
 34  Array pushback/popback (#51)
 33  Consistent struct/class sizeof (#40)
 32  associative arrays by index (#16)
 31  black box unit testing (#8)
 29  Pass value params byref (#34)
 29  Non-Static isExpression (#37)
 28  unit test & code separation (#7)
 28  coherent assoc. array syntax (#20)
 27  Explicit module `friendship` (#43)
 27  auto-member objects (#45)
 27  L-Value return (#73)
 25  Renaming ctor/dtor (#17)
 24  Explicit property keyword (#83)
 23  Unit test measurements (#9)
 23  Conditional syncronized (#30)
 22  struct constructor (#97)
 22  Variadic arguments re-passing (#102)
 20  User-defined sync function (#31)
 20  Named keyword arguments (#87)
 19  proper cast operators (#21)
 18  Iterators and Generators (#58)
 17  Small Exectables (#88)
 16  Pascal like sets (#61)
 15  Built-in variant type (#56)
 15  if, while, true, false, int (#86)
 14  D library contest (#59)
 14  Inline enum declaration (#76)
 13  Precise names for floats (#62)
 13  No Postfix Array Declarations (#85)
 12  Call log (#47)
 11  imag and comp FP types. (#63)
 11  Meta Information (#69)
 11  modules must not rely on files (#84)
 11  range type (#106)
 10  inout variable and return (#60)
 10  conv() and opConv (#66)
 10  interface to C++ (#71)
 10  Multi-Dimensional Allocation (#109)
 10  Full lexical closures (#140)
 9  Against class instance sizeof (#48)
 9  Improve module architecture (#64)
 9  copy operator (#95)
 8  inline expansion (#67)
 8  Finite sets (#72)
 8  opCast overloading (#81)
 8  function inheritance (#92)
 7  Relational class/array algebra (#65)
 7  In flight exception detection (#101)
 7  Real C bitfields (#145)
 6  garbage collection switch  (#96)
 5  date/time/datetime literal (#105)
 4  Declaration in function calls (#74)
 4  support struct&array in switch (#99)
 4  named tuple (#103)
 4  void Class.Method() {} syntax (#146)
 3  array in template arguments (#91)
 3  System.Windows.Forms (#93)
 3  Statically check for == null (#98)
 3  Reallocation Keyword (#108)
 3  Explicit out/inout/lazy (#110)
 3  First-class continuations (#141)
 2  Manage .resources files (#70)
 2  Multistep return (#75)
 2  constant operater overloading (#100)
 2  solve interdepend static this (#107)
 2  Quick For Syntax (#142)
 2  Implicit New (#143)
 2  Property shortcut (#144)
 2  Efficient array opCatAssign (#148)
 2  static foreach(scope/unscope) (#152)
 1  consistant new (#77)
 1  Parallel Scavenging GC (#80)
 1  function call over network (#111)
 1  temp alias param specialize (#112)
 1  Better UTF32 Support (#113)
 1  remove initializers (#147)
 1  variable template(short syntax (#149)
 1  template literal (#150)
 1  tuple literal and append-op (#151)
 1  __traits (#153)
 1  ext property for  basic types (#154)
 1  temporary variable (#155)
 1  invariant function (#156)
 1  constant member functions (#158)
 1  in for arrays (#160)
 1  in for arrays (#161)
 1  Custom Syntax (#163)
 0  Dynamic Conditional (#157)
 0  Custom Attributes (#159)
 0  Keyword Pow Operator (#162)
 0  templated constructors (#164)


Why is anyone complaining about cast?  I like it much better than Java/C++'s
version.
It makes it clear what you are doing.

Tuple return types would be extremely nice, but I guess out parameters will
have to do (not a fan)