Skip to content
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.

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

chore: adding benchmark for worst case #40

Merged
merged 1 commit into from
Feb 14, 2023
Merged

Conversation

abettini
Copy link
Contributor

@abettini abettini commented Feb 6, 2023

Co-authored-by: Michael Di Prisco Cadienvan@users.noreply.github.com

Co-authored-by: Michael Di Prisco <Cadienvan@users.noreply.github.com>
This was linked to issues Feb 6, 2023
Copy link
Collaborator

@rollsappletree rollsappletree left a comment

Choose a reason for hiding this comment

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

Sounds Good To Me!

@Cadienvan Cadienvan merged commit b511df0 into main Feb 14, 2023
@Cadienvan Cadienvan deleted the feat/benchmark_worst_case branch February 14, 2023 11:27
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.

Benchmark worst case Math.random speed issues
3 participants