https://issues.dlang.org/show_bug.cgi?id=16459
RazvanN <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |[email protected] Resolution|--- |WORKSFORME --- Comment #1 from RazvanN <[email protected]> --- This seems to have been improved now. In the first case it gives: test.d(14): Error: no property `doSomething` for `someObject` of type `test.SomeObject!int` test.d(14): potentially malformed `opDispatch`. Use an explicit instantiation to get a better error message So, at least it gives you a hint that this may be the problem. The idea is that currently the compiler cannot know if the error comes from passing the wrong arguments to opDispatch or if the error comes from within the innards of opDispatch that is why it just asks the user to call opDispatch explicitly. I think that until we find a way to deal with opDispatch this should be enough. --
