proposal-ptc-syntax
TypeScript
proposal-ptc-syntax | TypeScript | |
---|---|---|
8 | 1,305 | |
165 | 98,060 | |
0.6% | 0.6% | |
0.0 | 9.9 | |
almost 8 years ago | 4 days ago | |
HTML | TypeScript | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal-ptc-syntax
-
Time, Space and Complexity
The proposal of "syntactic tail calls" to provide an explicit syntax for tail calls, co-championed by committee members from Mozilla (responsible for SpiderMonkey, the engine of Firefox) and Microsoft, was a response to these concerns. However, this proposal is now listed among the TC39's inactive proposals, possibly due to diminished interest, which may stem from the infrequent use of tail recursive functions in JavaScript.
-
Bun, JavaScript, and TCO
This is not actually about Tail Call Optimisation, which is more flexible and optional matter of optimisation, but about Proper Tail Calls, which are actually part of the ECMAScript 6 specification (over implementer objections)—in strict mode, calls in tail position must not create additional stack frames. This is the last piece of ECMAScript 6 that most engines haven’t implemented, because it’s rather controversial: it actually causes some performance problems, and makes debugging harder, and may have security issues (in 2016, Mozilla declared it impossible to implement across realm boundaries due to their security model).
https://github.com/tc39/proposal-ptc-syntax has a lot of useful information about it all, and a proposal to make it explicit in syntax, such as with `return continue …`.
(Fun terminology problems here. The term TCO is commonly used for PTC, and PTC is very close to being a subset of TCO, but the mandatory stack frame elision which ruins debugging feels to me like it falls outside of TCO. In various situations, debuggers will mark things like “stack frame omitted” when they’ve optimised one out of existence, but you can generally compile things differently, or something like that, to prevent this. But with PTC, it feels like the engine is kinda not even allowed to know that a stack frames may be absent. So I say PTC and TCO are a little distinct, though PTC is mostly just a subset of TCO. Reminds me of the terminology of tree-shaking versus dead code removal—where the former is essentially a subset of the latter, but that the effects are just slightly different, though I’d say it’s more slight in that case than this.)
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]
While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535
For the version of it that is backwards compatible, they wouldn’t need to do anything other than recognise it as valid syntax. Their main concern is that it "could add confusion with very little benefit."
-
What happened to proper tail calls in JavaScript? (2021)
The spec for STC has a critique of PTC:
- performance
- developer tools
- Error.stack
- cross-realm tail calls
- developer intent
See: https://github.com/tc39/proposal-ptc-syntax#issues-with-ptc
Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535
- STC is part of the spec and will take too long to change.
- Now that they've implemented support for PTC, they don't want to regress web pages that rely on it.
- They don't want to discourage vendors from implementing PTC by agreeing to STC.
- They don't want to introduce confusion.
Some of these arguments about confusion and delays seem wrong hindsight, since on every point things would have been better if they'd just agreed to the compromise of STC.
- It would have been part of the spec years ago
- STC would have had a clear way for web pages to know when tail calls could be relied on (and PTC would have been optional)
- Other vendors didn't implement PTC in any case, despite no agreement on STC
- There's even more confusion as things are now
-
@lrvick bought the expired domain name for the 'foreach' NPM package maintainer. He now controls the package which 2.2m packages depend on.
You can see a direct example of this with Proper Tail Calls (PTC). It was added to the ECMAScript spec in 2015 as part of es6, but as of today - 7 years later - only Safari has shipped it*. As a result it is effectively not a thing in JavaScript, and the followup proposal meant to address issues with PTC ("Syntactic Tail Calls") has been basically ignored because PTC is already in the spec.
-
Node.js 14 is over 20x faster than Python3.8 for fib(n)
V8 implemented tail call optimization in the past, and the V8 team backed the TC39 proposal for syntactic tail calls (where you'd write return continue func() to make the use of TCO explicit). In Node 6 and 7 we could use them with the flag --harmony-tailcalls. The feature was removed from Node 8 after that proposal didn't go anywhere, but it's interesting, and shows some interest.
TypeScript
-
JSR Is Not Another Package Manager
Regular expressions are part of the language, so it's not so unreasonable that TypeScript should parse them and take their semantics into account. Indeed, TypeScript 5.5 will include [new support for syntax checking of regular expressions](https://github.com/microsoft/TypeScript/pull/55600), and presumably they'll eventually be able to solve the problem the GP highlighted on top of those foundations.
-
TypeScript Essentials: Distinguishing Types with Branding
Dedicated syntax for creating unique subsets of a type that denote a particular refinement is a longstanding ask[2] - and very useful, we've experimented with implementations.[3]
I don't think it has any relation to runtime type checking at all. It's refinement types, [4] or newtypes[5] depending on the details and how you shape it.
[1] https://github.com/microsoft/TypeScript/blob/main/src/compil...
-
What is an Abstract Syntax Tree in Programming?
GitHub | Website
-
Smart Contract Programming Languages: sCrypt vs. Solidity
Learning Curve and Developer Tooling sCrypt is an embedded Domain Specific Language (eDSL) based on TypeScript. It is strictly a subset of TypeScript, so all sCrypt code is valid TypeScript. TypeScript is chosen as the host language because it provides an easy, familiar language (JavaScript), but with type safety. There’s an abundance of learning materials available for TypeScript and thus sCrypt, including online tutorials, courses, documentation, and community support. This makes it relatively easy for beginners to start learning. It also has a vast ecosystem with numerous libraries and frameworks (e.g., React, Angular, Vue) that can simplify development and integration with Web2 applications.
-
Understanding the Difference Between Type and Interface in TypeScript
As a JavaScript or TypeScript developer, you might have come across the terms type and interface when working with complex data structures or defining custom types. While both serve similar purposes, they have distinct characteristics that influence when to use them. In this blog post, we'll delve into the differences between types and interfaces in TypeScript, providing examples to aid your understanding.
-
Type-Safe Fetch with Next.js, Strapi, and OpenAPI
TypeScript helps you in many ways in the context of a JavaScript app. It makes it easier to consume interfaces of any type.
- Proposal: Types as Configuration
-
How to scrape Amazon products
In this guide, we'll be extracting information from Amazon product pages using the power of TypeScript in combination with the Cheerio and Crawlee libraries. We'll explore how to retrieve and extract detailed product data such as titles, prices, image URLs, and more from Amazon's vast marketplace. We'll also discuss handling potential blocking issues that may arise during the scraping process.
-
Shared Tailwind Setup For Micro Frontend Application with Nx Workspace
TypeScript
-
Building a Dynamic Job Board with Issues Github, Next.js, Tailwind CSS and MobX-State-Tree
Familiarity with TypeScript, React and Next.js
What are some alternatives?
ecma262 - Status, process, and documents for ECMA-262
zod - TypeScript-first schema validation with static type inference
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
Elixir - Elixir is a dynamic, functional language for building scalable and maintainable applications
Tailwind CSS - A utility-first CSS framework for rapid UI development.
constant-time - Constant-time WebAssembly
zx - A tool for writing better scripts
foreach - Foreach component + npm package
esbuild - An extremely fast bundler for the web
rr - Record and Replay Framework
gray-matter - Smarter YAML front matter parser, used by metalsmith, Gatsby, Netlify, Assemble, mapbox-gl, phenomic, vuejs vitepress, TinaCMS, Shopify Polaris, Ant Design, Astro, hashicorp, garden, slidev, saber, sourcegraph, and many others. Simple to use, and battle tested. Parses YAML by default but can also parse JSON Front Matter, Coffee Front Matter, TOML Front Matter, and has support for custom parsers. Please follow gray-matter's author: https://github.com/jonschlinkert