Add --expand option to rustc to pretty-print expanded code.
#730
Conversation
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
pdietl
pushed a commit
to pdietl/rust
that referenced
this pull request
Apr 23, 2020
…-gate introduce feature gate into never-type test
tesuji
pushed a commit
to tesuji/rustc
that referenced
this pull request
Jun 9, 2020
Cleanup: Use rustc's `same_type` for our `same_tys` This delegates our `same_tys` to [ty::TyS::same_type][same_type] to remove some duplication. Our `same_tys` was introduced 4 years ago in rust-lang#730. Before, it was building an inference context to be able to call `can_eq` to compare the types. The `rustc-dev-guide` has some more details about `can_eq` in [Type Inference -> Trying equality][try_eq]. Now, using the rustc function, we are essentially comparing the `DefId`s of the given types, which also makes more sense, IMO. I also confirmed that the FIXME is resolved via a bit of `dbg!`, however no UI tests seem to have been affected. [same_type]: https://github.com/rust-lang/rust/blob/659951c4a0d7450e43f61c61c0e87d0ceae17087/src/librustc_middle/ty/util.rs#L777 [try_eq]: https://rustc-dev-guide.rust-lang.org/type-inference.html#trying-equality --- changelog: none
ZuseZ4
pushed a commit
to EnzymeAD/rust
that referenced
this pull request
Mar 7, 2023
* Bootstrap enzyme tblgen * Update .packaging/build_tarballs.jl * Fix tablgen exe * only set tblgen if empty * Fix * Update .packaging/build_tarballs.jl Co-authored-by: Valentin Churavy <[email protected]> Co-authored-by: William S. Moses <[email protected]>
celinval
added a commit
to celinval/rust-dev
that referenced
this pull request
Jun 4, 2024
Add a fixme testcase that can be used to reproduce the issue rust-lang#729.
tgross35
added a commit
to tgross35/rust
that referenced
this pull request
Jun 3, 2025
Disable `f16` on platforms that have recursion problems
noscripter
pushed a commit
to noscripter/rust
that referenced
this pull request
Sep 8, 2025
* feat: implement Rat in Maze * ref: rewrite tests using macro * chore(docs): add `rat_in_maze` to `DIRECTORY.md` * fix: fix clippy issues * chore(ref): update implementation - Remove bad comments - Add some tests * ref: handle improper maze * ref: change `maze` representation from `Vec<Vec<usize>>` to `Vec<Vec<bool>>` * ref: refactor maze cell validation for clarity and efficiency * ref: refactor rat in maze implementation - Add custom errors to handle various exception cases: empty maze, non-rectangle maze, start out of maze bound - Add edge tests to handle various types of maze * ref: update implementation - Add `maze_with_going_back` test - Add explaination of why return this solution and not the other one when multiple path exist in maze --------- Co-authored-by: Piotr Idzik <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.