-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Use benchmarks to set up a website tracking rust performance #14661
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Hey @brson, it looks like it might be possible to build on http://huonw.github.io/isrustfastyet/mem/ . Is that sort of what you're thinking? |
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#635 |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Apr 22, 2025
Fixes rust-lang/rust-clippy#14660 changelog: none
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
May 8, 2025
Fixes rust-lang/rust-clippy#14660 changelog: none
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
May 9, 2025
Fixes rust-lang/rust-clippy#14660 changelog: none
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Like http://speed.pypy.org/. This will require someone in moco to image a physical machine and set up a new buildbot builder before it makes any progress.
The text was updated successfully, but these errors were encountered: