News for hackers. Stuff that matters.
Re:What’s New in ES2019 by phpnode on Tuesday July 30, 2019 @08:18AM (#20564115)
Pattern matching is a really important feature but I strongly dislike that proposal because it feels like it introduces a bunch of single purpose syntax that's going to restrict the ability to evolve the language in future. It feels like it's an addon, not a holistic solution.

I would much, much rather that type annotation syntax gets standardised first, because it is comparatively easy to build pattern matching when that's in place but going the opposite direction is difficult. What is a type if not a pattern?

Re:What’s New in ES2019 by pas on Tuesday July 30, 2019 @09:25AM (#20564586)
It seems that only `when` and `->`is the new syntax, no? The arrow seems something that could be replaced with `=>`, but anyway, neither seems to be very restrictive with regards to future syntax. (After all they are only defined in a `case` context, so the can be reused for whatever future purpose outside.)

Plus it's a stage1 proposal, meaning it's far from serious.

Could you link the type annotation proposal, I can't find it.

Re:What’s New in ES2019 by snek on Tuesday July 30, 2019 @10:27AM (#20565094)
There is no type annotation proposal.
Re:What’s New in ES2019 by sdegutis on Tuesday July 30, 2019 @11:13AM (#20565558)
TypeScript is becoming the de facto type annotations proposal.
Re:What’s New in ES2019 by Roboprog on Tuesday July 30, 2019 @05:31PM (#20569406)
Let me know when (type inference of) partial function application and object literals are easy in Typescript and I’ll consider it.
Re:What’s New in ES2019 by sdegutis on Tuesday July 30, 2019 @06:10PM (#20569720)
Do you have a specific example of code that's hard to annotate in TypeScript? I've been using it for about a year without major issues (except somewhat slow compile times).
Re:What’s New in ES2019 by Roboprog on Wednesday July 31, 2019 @02:51PM (#20577089)
Re:What’s New in ES2019 by snek on Tuesday July 30, 2019 @10:26AM (#20565087)
In JS, the pattern is the type. That is the point of duck typing.
Re:What’s New in ES2019 by SomeOldThrow on Tuesday July 30, 2019 @04:28PM (#20568783)
> In JS, the pattern is the type.

How do you match against a `Buffer` pattern/type?

Re:What’s New in ES2019 by vimslayer on Wednesday July 31, 2019 @01:30AM (#20571907)
In the current proposal,

    case (value) {
        when { constructor: Buffer } ->
            console.log("It's a Buffer!")
    }
that doesn't handle subtying though and doesn't work across realms.
Re:What’s New in ES2019 by SomeOldThrow on Wednesday July 31, 2019 @01:35AM (#20571921)
Oh interesting you can match on that!

However I think my point stands that javascript has runtime conceptions of types that go beyond duck typing.