|
If you were logged in you would be able to see more operations.
|
|
|
Boo
Created: 08/Nov/05 07:08 PM
Updated: 08/Nov/05 07:32 PM
|
|
| Component/s: |
Compiler
|
| Affects Version/s: |
0.7
|
| Fix Version/s: |
0.7.5
|
|
|
[19:53] <l33ts0n> the "meta object" returned by any() and all() overrides the most common comparison operators. It inherits IQuackFu. With -ducky I can access the members declared inside of the type; any members not declared in the type are sent through the IQuackFu interface.
[19:53] <l33ts0n> any([1, 2, 3]) > 0 goes through QuackInvoke instead of any.op_GreaterThan
[19:54] <bamboo> I see
[19:54] <bamboo> it's a bug then
[19:54] <bamboo> if the compiler can determine the proper operator to invoke
[19:54] <bamboo> it should
|
|
Description
|
[19:53] <l33ts0n> the "meta object" returned by any() and all() overrides the most common comparison operators. It inherits IQuackFu. With -ducky I can access the members declared inside of the type; any members not declared in the type are sent through the IQuackFu interface.
[19:53] <l33ts0n> any([1, 2, 3]) > 0 goes through QuackInvoke instead of any.op_GreaterThan
[19:54] <bamboo> I see
[19:54] <bamboo> it's a bug then
[19:54] <bamboo> if the compiler can determine the proper operator to invoke
[19:54] <bamboo> it should |
Show » |
| There are no comments yet on this issue.
|
|
Bug
Resolved
Major
binary operator overloading with ducky should invoke operator directly instead of calling QuackInvoke()