Skip to content

add 64-bit integer operations entry to stage 0 proposals table#222

Merged
rwaldron merged 1 commit intotc39:masterfrom
max-mapper:patch-1
Dec 1, 2015
Merged

add 64-bit integer operations entry to stage 0 proposals table#222
rwaldron merged 1 commit intotc39:masterfrom
max-mapper:patch-1

Conversation

@max-mapper
Copy link
Copy Markdown
Contributor

@indutny
Copy link
Copy Markdown

indutny commented Dec 1, 2015

Did we really missed this step? Gosh!

@rwaldron
Copy link
Copy Markdown
Contributor

rwaldron commented Dec 1, 2015

Thanks!

rwaldron added a commit that referenced this pull request Dec 1, 2015
add 64-bit integer operations entry to stage 0 proposals table
@rwaldron rwaldron merged commit aa7637f into tc39:master Dec 1, 2015
@domenic
Copy link
Copy Markdown
Member

domenic commented Dec 1, 2015

@BrendanEich are you still willing to champion this? Last I heard you didn't have time, and so it was withdrawn.

@allenwb
Copy link
Copy Markdown
Member

allenwb commented Dec 1, 2015

It seems to me that we should have room in our process for a proposal that remains sitting in Stage 0 waiting for a TC39 champion to step-up and push it forward.

Periodically, we might review the list of such proposals at a TC39 meeting and decided whether each one should remain "waiting for champion" or be purged.

@domenic
Copy link
Copy Markdown
Member

domenic commented Dec 1, 2015

Allen, that was not what we decided the bar was: https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md#proposals. This repo is for listing championed proposals.

@allenwb
Copy link
Copy Markdown
Member

allenwb commented Dec 1, 2015

@domenic But according to https://esdiscuss.org/topic/efficient-64-bit-arithmetic#content-7 (and presumably the corresponding meeting notes) it was already accepted by TC39 as a stage 0 proposal.

I don't believe that the withdraw of a champion because they are too busy or other wise unable to continue should result in the proposal being administratively deleted without any broad TC39 visibility.

Put it one the agenda for the next meeting and see what TC39, as a whole, wants to do with it.

@domenic
Copy link
Copy Markdown
Member

domenic commented Dec 1, 2015

Or we can just let it languish in stage 0 and make stage0.md not reflect reality; that's fine too instead of using up committee time.

@allenwb
Copy link
Copy Markdown
Member

allenwb commented Dec 1, 2015

@domenic I think we need to use up committee time, at least on this one. 64-bit support is important and if nobody on the committee is is interested in championing it that is a committee dysfunction that needs to be resolved.

@domenic
Copy link
Copy Markdown
Member

domenic commented Dec 1, 2015

OK, that's fair; thanks for taking the time to explain.

@max-mapper
Copy link
Copy Markdown
Contributor Author

Can someone point me to where the next agenda lives and I'll send a PR? Tried to find it but failed

@ljharb ljharb added the proposal This is related to a specific proposal, and will be closed/merged when the proposal reaches stage 4. label Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

proposal This is related to a specific proposal, and will be closed/merged when the proposal reaches stage 4.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants