TypeScript is surprisingly ok for compilers

Post by OrderlyTiamat » Sat, Aug 19, 2023, 9:05 AM UTC

nightpool wrote: post #187

flylikeabanana wrote: post #182

Earlier quoted context omitted.

FP in python is painful without tail call elimination and the higher-order function syntax is so clunky

JS also doesn't have TCE, but for Python even just the lambda limitations are surprisingly annoying. I can't tell you how many times i've been frustrated because it's nearly impossible to put a print statement into a python lambda

    map(lambda x: (x := func1(x), func2(x), None)[2], gen())

Post by grumblingdev » Sat, Aug 19, 2023, 12:29 PM UTC

throwaway287391 wrote: post #211

nightpool wrote: post #187

Earlier quoted context omitted.

JS also doesn't have TCE, but for Python even just the lambda limitations are surprisingly annoying. I can't tell you how many times i've been frustrated because it's nearly impossible to put a print statement into a python lambda

As a Python enjoyer, why do we want to shove so much into lambdas rather than just doing an inline function `def`? Is it the fact that you have to give it a name? If so I'd say just using some generic name like `{f,fn,func(tion),callback,etc}` is fine (at least as much as an anonymous function is), and to me would usually be more readable than an inline definition of a multi-statement lambda would be. Or maybe it's t…

    def foo():
      def run():
        print("hi")
      run()

    function foo() {
      run()
      function run() {
        console.log('hi')
      }
    }

Post by zdragnar » Sat, Aug 19, 2023, 2:06 PM UTC

shrimpx wrote: post #208

zdragnar wrote: post #132

Earlier quoted context omitted.

There are a few very specific differences. In a subclass, 'this' doesn't exist until you call "super" for example, and the constructor will throw an error of invoked without the "new" keyword. [O] These differences let you extend built-in things that simply can't be done with old prototype constructor syntax. [1] [O] I should probably be using a more recent reference like MDN, but the 2ality series always sticks out…

Thanks. It sounds like subclassing built-ins is where transpilers hit a hard wall. Other syntactic features of es6 can be transpiled.

Post by _ZeD_ » Sat, Aug 19, 2023, 2:30 PM UTC

grumblingdev wrote: post #233

throwaway287391 wrote: post #211

Earlier quoted context omitted.

As a Python enjoyer, why do we want to shove so much into lambdas rather than just doing an inline function `def`? Is it the fact that you have to give it a name? If so I'd say just using some generic name like `{f,fn,func(tion),callback,etc}` is fine (at least as much as an anonymous function is), and to me would usually be more readable than an inline definition of a multi-statement lambda would be. Or maybe it's t…

JS also kills Python for inline functions thanks to hoisting. It's much easier to follow the control flow with hoisting. I see `run()` being called, and then I want to know what it is. In other languages you are usually seeing a huge bunch of inline functions and then asking: okay, but when and how is this actually called? def foo(): def run(): print("hi") run() function foo() { run() function run() { console.log('hi…

Post by [deleted] » Sat, Aug 19, 2023, 11:23 PM UTC

madarco wrote: post #26

rtpg wrote: post #4

TS's type system is fun but a part of me always wonders how much faster TS's compiler would be if it was written in a compiled language (assuming "good implementation", which is a big assumption!)

PS: swc and esbuild aren't good example, because most of the speed improvements comes from the fact that they are just stripping TS-specific syntaxes to generate JS code. Also tsc is slow, sure, but only for the first run. Enabling `incremental` flag or using watch mode with `--transpile-only` usually brings compile time under 100ms, Making it practically indistinguishable from SWC or ESBuild.