PEP 735: Add prior art sections for JS and Ruby to appendices #3557
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This initial writeup covers two ecosystems' related work which should be understood as part of the sources and influences for this PEP.
I had previously documented the Ruby ecosystem a bit in a post on discourse, and had considered dropping JS as not having a complex enough related case. However, after starting to read the details carefully and write it down, it became clear that the JS cases are relatively nuanced and offer good related background.
The writeups reflect my current understanding of these systems and behaviors, and to the best of my ability contain no inaccuracies or guesses. That said, I very much welcome corrections to the content if I've made any mistakes.
I'll try to add more prior art information in the future. Rust, in particular, has surfaced as an ecosystem of interest.
📚 Documentation preview 📚: https://pep-previews--3557.org.readthedocs.build/