Consider: void foo(alias pred)() { pragma(msg, pred.stringof); } unittest { foo!((i) { return i < 0; })(); int z = 1; foo!((i) { return i < z; })(); } void main(string[] args) { } This outputs: __funcliteral1(__T2) __dgliteral3(__T4) because the first literal does not have to be a delegate.
(In reply to comment #0) > Consider: > > void foo(alias pred)() { > pragma(msg, pred.stringof); > } > > unittest { > foo!((i) { return i < 0; })(); > int z = 1; > foo!((i) { return i < z; })(); > } > > void main(string[] args) > { > } > > This outputs: > > __funcliteral1(__T2) > __dgliteral3(__T4) > > because the first literal does not have to be a delegate. I meant that right now this outputs: __dgliteral1(__T2) __dgliteral3(__T4) and it should output: __funcliteral1(__T2) __dgliteral3(__T4)
This is as designed. http://www.digitalmars.com/d/1.0/expression.html#FunctionLiteral "If the keywords function or delegate are omitted, it defaults to being a delegate." Having the type of a function/delegate literal depend on its contents like this makes it hard for someone reading the code to tell which it is. Since function pointers and delegates are not generally interchangeable, AISI it's desirable to keep their literal notations distinct.
(In reply to comment #2) > This is as designed. > > http://www.digitalmars.com/d/1.0/expression.html#FunctionLiteral > "If the keywords function or delegate are omitted, it defaults to being a > delegate." > > Having the type of a function/delegate literal depend on its contents like this > makes it hard for someone reading the code to tell which it is. Since function > pointers and delegates are not generally interchangeable, AISI it's desirable > to keep their literal notations distinct. I think type deduction should help here as much as anywhere else. If you do want a delegate, you can always use the delegate keyword. Plus, all algorithms in std.algorithm take an efficiency toll when used with literals.
(In reply to comment #2) > This is as designed. > > http://www.digitalmars.com/d/1.0/expression.html#FunctionLiteral > "If the keywords function or delegate are omitted, it defaults to being a > delegate." > > Having the type of a function/delegate literal depend on its contents like this > makes it hard for someone reading the code to tell which it is. Since function > pointers and delegates are not generally interchangeable, AISI it's desirable > to keep their literal notations distinct. I think type deduction should help here as much as anywhere else. If you do want a delegate, you can always use the delegate keyword. Plus, all algorithms in std.algorithm take an efficiency toll when used with literals. (Please do not mark this as resolved; I've discussed with Walter before posting it, and he suggested I do. In general, the spec of D2 is fluid enough to not be a strong reason for invalidating a bug report. Thanks.)
BTW this is in TDPL now, with Walter's approval.
The following example is in TDPL: unittest { auto f = (int i) {}; assert(is(f == function)); } The example fails to compile (it should). Also the following example should work: unittest { int a; auto f = (int i) { a = i; }; assert(is(f == delegate)); } The compiler should automatically infer function or delegate type depending on the literal's use of local state. The argument against it - people change a detail in the body of the function and its type changes - is non sequitur. Changing a literal from 10 to 10.0 also changes its type. Please fix.
https://github.com/D-Programming-Language/dmd/pull/588
https://github.com/D-Programming-Language/dmd/commit/c50eb5f5726a65efa1224ff0f0fd60acbb6e3027