watching your talk was like witnessing Fermats last theorem being proven...

the scheduler solution was brilliant and the semantic analysis of a mixin statement that resulted in a comprehensible error message blew my mind.

Here is a belated applause that should have happened during those slides.

Well done.

josh

On 05/24/2014 05:03 AM, Joshua Niehus wrote:
> watching your talk was like witnessing Fermats last theorem being proven...
>
> the scheduler solution was brilliant and the semantic analysis of a
> mixin statement that resulted in a comprehensible error message blew my
> mind.
>
> Here is a belated applause that should have happened during those slides.
>
> Well done.
>
> josh

Unfortunately, I missed the talk. Sounds promising (I'm using an explicit scheduler component for semantic analysis as well.) What does comprehensible mixin error message mean exactly?

On 05/24/2014 03:58 PM, Timon Gehr wrote:

> What does comprehensible mixin error message mean exactly?

deadalnix showed a piece of code that had a compilation error inside a mixin string that was mixed in by another mixin. The compiler was pointing out the exact column of the mixed in error, as well as all the inclusion backtrace.

Ali

On 5/24/2014 10:41 PM, Ali Çehreli wrote:
> On 05/24/2014 03:58 PM, Timon Gehr wrote:
>
>  > What does comprehensible mixin error message mean exactly?
>
> deadalnix showed a piece of code that had a compilation error inside a
> mixin string that was mixed in by another mixin. The compiler was
> pointing out the exact column of the mixed in error, as well as all the
> inclusion backtrace.
>

DAT DIAGNOSTIC!  o_O

On Saturday, 24 May 2014 at 03:03:56 UTC, Joshua Niehus wrote:
> watching your talk was like witnessing Fermats last theorem being proven...
>
> the scheduler solution was brilliant and the semantic analysis of a mixin statement that resulted in a comprehensible error message blew my mind.
>
> Here is a belated applause that should have happened during those slides.
>
> Well done.
>
> josh

Hi,

I'm not sure how much this is a reference to the 'upworthy' slide and how much you were impressed, but whatever the ratio, thank you.

On Saturday, 24 May 2014 at 22:58:26 UTC, Timon Gehr wrote:
> On 05/24/2014 05:03 AM, Joshua Niehus wrote:
>> watching your talk was like witnessing Fermats last theorem being proven...
>>
>> the scheduler solution was brilliant and the semantic analysis of a
>> mixin statement that resulted in a comprehensible error message blew my
>> mind.
>>
>> Here is a belated applause that should have happened during those slides.
>>
>> Well done.
>>
>> josh
>
> Unfortunately, I missed the talk. Sounds promising (I'm using an explicit scheduler component for semantic analysis as well.) What does comprehensible mixin error message mean exactly?

I think the talk will be available, but as it was the last one, probably in a long time :(

The mixin thing was an explanation of what the compiler does when it encounter error within mixins. Basically, it show the error message with the "mixed" in code, and show the mixin where that code come from.

On Saturday, 24 May 2014 at 03:03:56 UTC, Joshua Niehus wrote:
> watching your talk was like witnessing Fermats last theorem being proven...
>
> the scheduler solution was brilliant and the semantic analysis of a mixin statement that resulted in a comprehensible error message blew my mind.
>
> Here is a belated applause that should have happened during those slides.
>
> Well done.
>
> josh

Also, while we are at it, thank to David Ellsworth, for his great picture of Andrei. Now we will be able to advertise massively on the net (if you don't understand any of this, you'll know soon).

On Sun, 25 May 2014 07:46:48 +0000
deadalnix via Digitalmars-d <digitalmars-d@puremagic.com> wrote:

> The mixin thing was an explanation of what the compiler does when it encounter error within mixins. Basically, it show the error message with the "mixed" in code, and show the mixin where that code come from.

Once SDC is completed, that will likely be a huge leg-up over dmd, given how poorly it handles those.

- Jonathan M Davis