Uh oh!
There was an error while loading. Please reload this page.
Cleanup - #280
Closed
brson wants to merge 3 commits into
Closed
Conversation
graydon
commented
Mar 22, 2011
Contributor
Integrated. |
oli-obk added a commit
to oli-obk/rust
that referenced
this pull request
Sep 19, 2017
Produce backtraces for miri internals
keeperofdakeys pushed a commit
to keeperofdakeys/rust
that referenced
this pull request
Dec 12, 2017
Refine defininition of mcontext_t on linux glibc x86-64 and x86.
kazcw pushed a commit
to kazcw/rust
that referenced
this pull request
Oct 23, 2018
* Implement `_m_psubb` * Implement `_m_psubw` * Implement `_m_psubd` * Implement `_m_psubsb` * Implement `_m_psubsw` * Implement `_m_psubusb` * Implement `_m_psubusw` * Have the subtraction intrinsic naming consistent with the addition ones E.g. use `_mm_sub_pi8` instead of `_m_psubb` * Implement all subtraction aliases for the `_mm_*` variants - `_m_psubb` for `_mm_sub_pi8` - `_m_psubw` for `_mm_sub_pi16` - `_m_psubd` for `_mm_sub_pi32` - `_m_psubsb` for `_mm_subs_pi8` - `_m_psubsw` for `_mm_subs_pi16` - `_m_psubusb` for `_mm_subs_pu8` - `_m_psubusw` for `_mm_subs_pu16`
workingjubilee pushed a commit
to workingjubilee/rustc
that referenced
this pull request
Jul 20, 2022
…fety Document unsafety
celinval pushed a commit
to celinval/rust-dev
that referenced
this pull request
Jun 4, 2024
* Add support for multiple expected failures. * Check for expected failures on RMC's output instead of test file. * Address concerns.
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
280: Fixed cast expression parsing in ra_syntax. r=matklad a=ruabmbua Fixesrust-lang#279 Related to rust-lang/rust-analyzer#273 The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). **Example:** ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes the plus sign after path types as extra type bounds. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`. Co-authored-by: Roland Ruckerbauer <roland.rucky@gmail.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update docs for 'if' statements, remove redundant alt cases, expand elseif tests.