Skip to content

remove entries for proposals that were never presented - #605

Open
michaelficarra wants to merge 1 commit into
mainfrom
michaelficarra-patch-1
Open

remove entries for proposals that were never presented#605
michaelficarra wants to merge 1 commit into
mainfrom
michaelficarra-patch-1

Conversation

@michaelficarra

Copy link
Copy Markdown
Member

The description of this document states

Inactive proposals are proposals that at one point were presented to the committee but were subsequently abandoned, withdrawn, or rejected.

As a follow-up, we should mark each entry with one of those 3 statuses.

Comment thread inactive-proposals.md
| [TypedArray stride parameter][typedarray-stride-parameter] | Shu-yu Guo | Withdrawn: concern about performance implications, and the proposal is not expressive enough | <sub>&nbsp;-[2020&#8209;09][typedarray-stride-parameter-notes]<br />&nbsp;-[2020&#8209;03][typedarray-stride-parameter-notes-2020-03]</sub> |
| [Unused Function Parameters][unused-params] | Gus Caplan | Rejected: the need to solve the problem does not outweigh the hazards | <sub>&nbsp;-[2020&#8209;09][unused-params-notes]</sub> |
| [Improving iteration on Objects][object-iteration] | Jonathan Keslin | Withdrawn: concern about need for such an API | <sub>&nbsp;-[2020&#8209;02][object-iteration-notes]</sub> |
| [`String.prototype.at`][string-at] | Mathias Bynens<br />Rick Waldron | Obsoleted by renamed `String.prototype.item` proposal | <sub>Never presented</sub> |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i could have sworn this was actually presented pre ES6; i can't load https//wiki.ecmascript.org/doku.php?id=strawman:string_at (or on archive.org) to check though

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It says never presented, so I trusted it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added that in 87e98c8, likely because it wasn't present in the notes, but that doesn't mean it's correct.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The notes are the canonical record of the committee's work, so I think "not present in the notes" is the actual standard we should use.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be a reasonable change to make, although it'd preclude anything presented before ~2012 that hadn't been presented since, but at this point that's probably ok.

@michaelficarra
michaelficarra force-pushed the michaelficarra-patch-1 branch from 9564755 to d24a2af Compare July 10, 2026 17:27
@michaelficarra
michaelficarra force-pushed the michaelficarra-patch-1 branch 2 times, most recently from c44d18f to 091a5ef Compare July 22, 2026 02:10
Comment thread inactive-proposals.md
| [RegExp Atomic Groups & Possessive Quantifiers][re-atomic-groups] | Justin Ridgewell | engines are not interested in the feature, mainly because it doesn't solve backtracking for most users | <sub>&nbsp;-[2021&#8209;10][re-atomic-groups-notes]</sub> |
| [RefCollection][refcollection] | Robin Ricard | Withdrawn; replaced with [Symbols as WeakMap keys][symbols-weakmap]; also there were OCAP/membrane concerns around providing a globally available pre-instantiated RefCollection | <sub>&nbsp;-[2020&#8209;04][refcollection-notes]</sub> |
| [Generic Comparison][spaceship] | Hemanth HM<br />Jordan Harband | Withdrawn: replaced with [Array Equality][array-equality] | <sub>&nbsp;-[2020&#8209;06][spaceship-notes]</sub> |
| [`from ... import`][fromimport] | Bradley Farias | Never presented; preliminary feedback about syntax cost not being worth the weight | <sub>Never presented</sub> |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this is worth keeping here; maybe it'd be better to tweak the heading text to allow for never-presented proposals from delegates who got negative feedback prior to presenting?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the purpose of this repo is for formal record. There is no formal record of this proposal being presented, so I don't think it belongs.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, but there's a repo - https://github.com/bmeck/proposal-from-import - and this helps ensure that if anyone tries to bring the idea back, they have context. The repo doesn't have to confine itself to plenaries - it's a tool, and it can do whatever's useful.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sure there's plenty of community-authored proposals that would also be helpful links for anyone who independently has the same idea. I just don't think this is the right place to aggregate them. This repo, IMO, is an official historical record of this committee's work. And from the committee's perspective, these proposals don't exist.

@michaelficarra
michaelficarra force-pushed the michaelficarra-patch-1 branch from 091a5ef to 94b380d Compare July 24, 2026 03:37
@michaelficarra
michaelficarra force-pushed the michaelficarra-patch-1 branch from 94b380d to 38b30f5 Compare July 24, 2026 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants