Daniel Ehrenberg
Daniel Ehrenberg
TC39 is working on [infrastructure for built-in modules](https://github.com/tc39/proposal-javascript-standard-library/), which could be used to expand the standard library. Complementary to that, there are a number of things which are shared between...
Discussion is ongoing at https://github.com/tc39/proposal-javascript-standard-library/issues/14 about whether we should use one or multiple namespaces/scopes/schemes for built-in modules. If we use multiple, then this repository should consider being a place where...
Looking at the source of this module, it seems to transform `x |> f` directly into `f(x)`. However, any standardized proposal will likely evaluate `x` first, before `f`.
Test262 is another test suite for JavaScript. It provides a number of very detailed set of around 20k tests and aims to test every line in the specification, going into...
> In this design, if the "constructor" method definition is made static, then it is initialized to point at itself. What does this wording mean, that the constructor has a...
I like the aesthetics of having own methods to "complete the grid" and make an orthogonal system, but I'm wondering about the usage of this feature. I've heard from @sebmarkbage...
Should we have these? In particular, for a use case, some frameworks (cc @wycats @diervo) have mentioned a desire to have a way to observe changes in private fields. The...
`@namespace/module` is a frequently used convention in the JS ecosystem. Could we use it for layered APIs? As an import specifier, it's not "taken" (i.e., it produces failure in [the...
What standards venue is the Layered APIs infrastructure being developed in? I see it noted in this repository that the plan is to eventually integrate it into the HTML specification,...
It seems like this repo is subsumed by https://github.com/std-proposal/temporal . We should probably archive this repo and note its status in the README.