snek

@bakkot the reason to allow `super()` was to keep the distinction that syntax controls when super is allowed. there was also some other stuff about like class factories or something,...

would it be breaking to remove the early error forbidding super in classes without heritage? we could remove the special case in SuperCall for `null`, prototypes of base classes being...

I put this on the agenda for next meeting. I'd like to come to a conclusion about what we want to do with `extends null`. I'll try to put together...

@Jamesernator aside from it being the wrong prototype (which you noted), it also forgets about the second prototype (`Foo.__proto__`) @bathos I would be surprised if more than like 3 people...

If it's an array you can do `urls.values().reduce(...)`

i'm a fan of `import { Instant } from time;`. i can't really even imagine a case where we need more than a single identifier there. if we wanted to...

why would you ever need to dynamically import standard modules?

technically, the way the spec is currently written, you can resolve and link a module graph synchronously.

I'd be in favor of not having explicit versions. The current process for developing the spec is very rigorous, and the system it uses for introducing changes makes a lot...

From a high level I'd be fine with either a lazy api or passing the object into the constructor. A hook that is just called immediately in the constructor seems...