Re: Get compilation errors within opDispatch?

2020-02-17 Thread cc via Digitalmars-d-learn
On Monday, 17 February 2020 at 17:01:12 UTC, Adam D. Ruppe wrote: It sometimes helps to write it out log-form foo.opDispatch!"hello"(5); should give the full error. this btw is one of the most annoying missing errors in d... This worked, thank you! On Monday, 17 February 2020 at 16:45:53 U

Re: Get compilation errors within opDispatch?

2020-02-17 Thread Adam D. Ruppe via Digitalmars-d-learn
On Monday, 17 February 2020 at 16:41:54 UTC, cc wrote: Foo foo; foo.hello(5); Result: Error: no property `hello` for type `Foo` It sometimes helps to write it out log-form foo.opDispatch!"hello"(5); should give the full error. this btw is one of the most annoying missing errors in d...

Re: Get compilation errors within opDispatch?

2020-02-17 Thread Ali Çehreli via Digitalmars-d-learn
On 2/17/20 8:41 AM, cc wrote: Is there any way to see the compilation errors that occurred within an opDispatch template? struct Foo { void opDispatch(string s, SA...)(SA sargs) {     literally anything; } } Foo foo; foo.hello(5); Result:  Error: no property `hello` for type `Fo

Get compilation errors within opDispatch?

2020-02-17 Thread cc via Digitalmars-d-learn
Is there any way to see the compilation errors that occurred within an opDispatch template? struct Foo { void opDispatch(string s, SA...)(SA sargs) { literally anything; } } Foo foo; foo.hello(5); Result: Error: no property `hello` for type `Foo` Desired result