Is it OK that this repo merges static public fields, static private fields, and static private methods?

[littledan]

I created a single repository because creating multiple repositories seems confusing and complicated to do bookkeeping for. This repo comes from the November 2017 meeting when those three features were broken out from the class fields and private methods proposals. However, I'd be fine splitting out parts of it, if anyone thinks that is needed.

[littledan]

@gsathya raised this question again, in the context of the #10 proposal. It seems like static public fields are fairly settled, whereas lexical declarations in classes will take slightly more time to work through. Should we split off static public fields so as to not block them? At this point, I don't see much changing for static public fields.

[ljharb]

Splitting off static public into its own repo seems like a good idea.

[justsml]

Is there any push to break up these features still? @ljharb

It seems private semantics needs a lot more consideration...

[ljharb]

@justsml no, since all features are now stage 3, they should all be in the same repo, and will hopefully all advance together.

[littledan]

@justsml To clarify, in the May 2018 TC39 meeting, we settled on consensus on this proposal within TC39.

[littledan]

Closing per #3 (comment)