Anders Hejlsberg on Modern Compiler Construction (2016) [video]

Post by charlieflowers » Fri, Jun 15, 2018, 4:26 AM UTC

Touche wrote: post #24

iainmerrick wrote: post #18

There's so much that's great about C#, and that results from really smart, pragmatic, forward-looking language design, that I find it surprising how many aspects of C# development are hampered by really bad design. Specifically, the backwards compatibility story of the standard library is a mess (all the different .NET Framework versions, or wait, do I mean .NET Standard, or WinRT, or...?) and the package manager (Nu…

Every time I hear someone say that C# is a well designed language I think of the story of how they had to hack the compiler to get async/await to work, and how F# implemented the same feature as a library. I guess there are different levels of "well designed".

Post by vqrs » Sun, Jun 17, 2018, 3:58 PM UTC

stareatgoats wrote: post #40

stephen82 wrote: post #38

Earlier quoted context omitted.

Of course this would not work. typeof(true) is of type 'Boolean' and typeof(1) is of type 'number'. Do they compare to the same type? Nope, therefore is false in both cases. Try the following: let foo = true; true === foo === true; // returns true.

er - no. Assuming you are not trolling (benefit of the doubt and all that): You might mean it shouldn't work? but alas it does (because of 'lopsided equality tables'). Try the following: open the console of your browser, type the following: true == 1 === true and press enter - tada! You can also check out this SO answer if you are sufficiently flabbergasted: https://stackoverflow.com/a/12236341

Post by stareatgoats » Tue, Jun 19, 2018, 12:00 PM UTC

vqrs wrote: post #43

stareatgoats wrote: post #40

Earlier quoted context omitted.

er - no. Assuming you are not trolling (benefit of the doubt and all that): You might mean it shouldn't work? but alas it does (because of 'lopsided equality tables'). Try the following: open the console of your browser, type the following: true == 1 === true and press enter - tada! You can also check out this SO answer if you are sufficiently flabbergasted: https://stackoverflow.com/a/12236341

I'm not sure how what you linked is related, but the only "surprising" thing here is probably `true == 1`. This evaluates to true, and because comparisons are left-associative, we have `(true == 1) === true` which reduces to `true === true`, which, unsurprisingly, is true.