For AI agents: the complete documentation index is available at /tc39-atlas/en/llms.txt, the full documentation bundle is available at /tc39-atlas/en/llms-full.txt, and this page is available as Markdown at /tc39-atlas/en/proposals/stage/1/proposal-reverseIterator.md.
TC39 Atlas
  • English

      • Reverse iteration S1

      Proposal details
      Proposal overview

      This proposal focuses on reverse iteration, aiming to provide a standardized way to iterate over data structures in reverse order. The provided README is a template for ECMAScript proposals and does not contain specific technical details about the solution or its maturity. The proposal appears to be in its initial stages, as the README outlines setup procedures rather than implementation specifics.

      Note

      The README below comes from the upstream repository and may contain outdated stage or status metadata. Use the proposal details above as the current source of truth.

      template-for-proposals

      A repository template for ECMAScript proposals.

      Before creating a proposal

      Please ensure the following:

      1. You are a member of TC39
      2. You have read the process document
      3. You have reviewed the existing proposals

      Create your proposal repo

      Follow these steps:

      1. Create your own repo, clone this one, and copy its contents into your repo. (Note: Do not fork this repo in GitHub's web interface, as that will later prevent transfer into the TC39 organization)
      2. Go to your repo settings “Options” page, under “GitHub Pages”, and set the source to the master branch and click Save.
        1. Ensure "Issues" is checked.
        2. Also, you probably want to disable "Wiki" and "Projects"
      3. Avoid merge conflicts with build process output files by running: 
        git config --local --add merge.output.driver true
git config --local --add merge.output.driver true
      4. Add a post-rewrite git hook to auto-rebuild the output on every commit: 
        cp hooks/post-rewrite .git/hooks/post-rewrite
chmod +x .git/hooks/post-rewrite

      Maintain your proposal repo

      1. Make your changes to spec.emu (ecmarkup uses HTML syntax, but is not HTML, so I strongly suggest not naming it ".html")
      2. Any commit that makes meaningful changes to the spec, should run npm run build and commit the resulting output.
      3. Whenever you update ecmarkup, run npm run build and commit any changes that come from that dependency.