Skip to content

Support multiple PRNG when generating values from the Workers #4826

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.

Sign up for GitHub

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

Jump to bottom
Open
dubzzz opened this issue Mar 25, 2024 · 2 comments
Open

Support multiple PRNG when generating values from the Workers #4826

dubzzz opened this issue Mar 25, 2024 · 2 comments
Labels
💡 Idea to investigate Non straightforward features that seems great but need to be assessed and designed carefully. 💥 Targeting unplanned major Breaking change for an upcoming major version, but not blocker for any major.

Comments

@dubzzz
Copy link
Owner

dubzzz commented Mar 25, 2024 •
edited
Loading

💡 Idea

Probably attach the name of the PRNG to the state and find a way to find the PRNG from its name

Follow-up for #4063
@dubzzz dubzzz added the 💥 Targeting unplanned major Breaking change for an upcoming major version, but not blocker for any major. label Mar 25, 2024
@dubzzz dubzzz added 💥 Targeting v4 Breaking change that should be part of the major version 4. and removed 💥 Targeting v4 Breaking change that should be part of the major version 4. labels Feb 27, 2025
@dubzzz
Copy link
Owner Author

dubzzz commented Mar 1, 2025

Let's postpone it to v5 knowing that we will probably issue v5 not that long after v4 to drop CJS support from the library and from our other libraries too (if not already done before).

@stale Stale
Copy link

stale bot commented Apr 30, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 30, 2025
@dubzzz dubzzz added 💡 Idea to investigate Non straightforward features that seems great but need to be assessed and designed carefully. and removed stale labels May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💡 Idea to investigate Non straightforward features that seems great but need to be assessed and designed carefully. 💥 Targeting unplanned major Breaking change for an upcoming major version, but not blocker for any major.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dubzzz