Repository navigation
SHA-1 implementation - #230
Merged
1 commit merged intoFeb 21, 2011
Merged
1 commit merged into
1 commit merged into
Conversation
oli-obk
added a commit
to oli-obk/rust
that referenced
this pull request
Jul 19, 2017
get cargo-miri to work
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this pull request
Dec 12, 2017
kazcw
pushed a commit
to kazcw/rust
that referenced
this pull request
Oct 23, 2018
* sse: add missing aliases _m_pextrw, _m_pinsrw, _m_pmovmskb, _m_pshufw * sse: _mm_maskmove_si64, _m_maskmovq * sse: _mm_mulhi_pu16, _m_pmulhuw * sse: _mm_avg_pu8, _m_pavgb * sse: _mm_avg_pu16, _m_pavgw * sse: _mm_sad_pu8, _m_psadbw * sse: _mm_cvtpi32_ps * sse: _mm_cvtpi32x2_ps
dlrobertson
pushed a commit
to dlrobertson/rust
that referenced
this pull request
Nov 29, 2018
…reference Add mention of RFC 2128 (use_nested_groups) in the reference
matthiaskrgr
pushed a commit
to matthiaskrgr/rust
that referenced
this pull request
Mar 7, 2023
Fix/simd bitmask
celinval
pushed a commit
to celinval/rust-dev
that referenced
this pull request
Jan 3, 2025
This harness takes between 22-25 minutes in CI. Change the harnesses's macro to use kissat solver instead, which brings verification time down to ~7 seconds. As an aside, I noticed this problem because the partition 1 runner in rust-lang#229 is taking ~55 minutes, where the other partitions are taking ~30 minutes. This harness accounts for almost the entire difference. One nice consequence of partitioning verification is that it will make performance issues like this more noticeable. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.
noscripter
pushed a commit
to noscripter/rust
that referenced
this pull request
Sep 8, 2025
U007D
pushed a commit
to U007D/rust-mos
that referenced
this pull request
Aug 21, 2026
375: Move renames into ra_analysis and rename the correct range r=DJMcNab a=DJMcNab Fixes rust-lang#230. Supersedes rust-lang#235. TODO: add some tests for this Co-authored-by: DJMcNab <36049421+djmcnab@users.noreply.github.com>
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Please review.
It's currently in a 'sha1' module, but maybe it belongs in 'crypto' or similar. Also, I haven't provided any way to convert the digest to a hex-formatted string. Do you have an opinion on where that belongs?