search

tc39 / proposal-built-in-modules

BSD 2-Clause "Simplified" License
892 stars 25 forks source link

Document scope #32

Closed bakkot closed 5 years ago

bakkot commented 5 years ago

To help people understand what sort of things the proposal covers (e.g. not syntax).

I didn't say "only things which could in principle be implemented in JS", though as I understand it that might be a constraint this proposal intends to have, in which case it should probably be documented more explicitly.

mattijs commented 5 years ago

Definitely a good idea to clarify the scope of the proposal, I should have included that from the start.

The actual goal of the proposal is not to talk about the contents of the standard library (concretely) but to describe the mechanism for the standard library and the semantics for using it. We've always viewed the contents of the standard library as a tangential and parallel effort outside of this proposal

Does it make sense to declare that under the Scrope section?

While I don't want to discourage discussion on the contents I don't want it to take away from defining the mechanism.

Mouvedia commented 5 years ago

Also redirect to #16 for "brainstorming";

bakkot commented 5 years ago

@mattijs rephrased, how's it look now?

(Feel free to push commits to this branch yourself, if you like.)

mattijs commented 5 years ago

This is great, thanks @bakkot

littledan commented 5 years ago

Sorry if I made this point confusing! If we get too many additional issues that are out of scope, maybe we should make an issue template as well.

StoneCypher commented 5 years ago

I don't actually understand why the things I wrote that were closed as out of scope are in fact out of scope

It seems like finishing the containers, the functional predicates, and having improved random number generation all fall well inside of this

bakkot commented 5 years ago

@StoneCypher, as it says in the PR, the main purpose of this repository is to discuss how such a library would work, not what would be in it. To keep the issue tracker usable for that purpose, let's keep specific suggestions for things to include mostly centralized in #16, at least for the moment.