Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

export-ns-from (Needs Consensus PR) #16

Open
1 task done
hzoo opened this issue Jul 27, 2017 · 9 comments
Open
1 task done

export-ns-from (Needs Consensus PR) #16

hzoo opened this issue Jul 27, 2017 · 9 comments

Comments

@hzoo
Copy link
Member

hzoo commented Jul 27, 2017

Champions: @jdalton @benjamn (prev @leebyron)
Spec Repo: https://github.com/leebyron/ecmascript-export-ns-from
Moved to Stage 2 at the July 2017 meeting: https://github.com/tc39/agendas/blob/master/2017/07.md
Approved as a needs consensus PR at Sept 2017 meeting (Stage 4) (tc39/ecma262#1005)

Syntax

export * as ns from 'mod';

Implementation

@jdalton
Copy link
Member

jdalton commented Jul 27, 2017

This is moving to a consensus PR (I'm unclear what stage that maps to).
That said, stage 2 sounds like a good place.

@ljharb
Copy link
Member

ljharb commented Jul 27, 2017

I'm going to update the proposal list to make it stage 2, and when it becomes a merged PR, i'll move it directly from there to "finished" - so "stage 2" is correct imo :-)

@leobalter
Copy link
Member

leobalter commented Jul 27, 2017 via email

@ljharb
Copy link
Member

ljharb commented Jul 27, 2017

To get to stage 3, the spec would need signoff, which is part of the PR review process - so it's not stage 3 until it's mergeable, and it's not stage 4 til it's merged - but it's stage 2 now.

@hzoo
Copy link
Member Author

hzoo commented Aug 8, 2017

Made an issue to split the proposals into 2 if anyone wants to comment more babel/babel#6075

This was referenced Sep 20, 2017
@hzoo hzoo changed the title export-ns-from (Stage 2) export-ns-from (Stage 4) Sep 28, 2017
@ljharb ljharb changed the title export-ns-from (Stage 4) export-ns-from (Needs Consensus PR) Mar 1, 2018
@ljharb
Copy link
Member

ljharb commented Mar 1, 2018

Updated the title to reflect that this no longer is a proposal, and thus has no stage, but can be landed as soon as it has consensus from the committee (which requires test262 tests)

@xtuc
Copy link
Member

xtuc commented Mar 2, 2018

Should we close it in the meantime? I feel like we have to many issues on this repo.

@jdalton
Copy link
Member

jdalton commented Mar 2, 2018

I'm 👎 on closing.

There's currently 26 open issues (not too bad considering Babel proper has ~500) and this is something that's totally valid.

@ljharb
Copy link
Member

ljharb commented Mar 2, 2018

I also think it should remain open; if we want to reduce the number of issues open on a repo, let’s fix all of the things they’re referencing instead of sweeping the problem under the rug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants