Removed ty_type (previously used to represent *tydesc). #12180
Merged
Conversation
This file contains 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
| @@ -520,19 +520,6 @@ pub fn val_ty(v: ValueRef) -> Type { | |||
| } | |||
| } | |||
|
|
|||
| // Let T be the content of a box @T. tuplify_box_ty(t) returns the | |||
| // representation of @T as a tuple (i.e., the ty::t version of what T_box() | |||
| // returns). | |||
There was a problem hiding this comment.
Is it intentional to delete this comment?
There was a problem hiding this comment.
I wanted to remove the function completely - it's only used by closure-related functions, the layout is wrong and the comment was a victim. I'll put it back if desired.
There was a problem hiding this comment.
All right if it was intentional.
|
r+ after rebase |
bors
added a commit
that referenced
this pull request
Feb 12, 2014
flip1995
pushed a commit
to flip1995/rust
that referenced
this pull request
Jan 25, 2024
Suggest existing configuration option if one is found While working on/testing rust-lang#12179, I made the mistake of using underscores instead of dashes for the field name in the clippy.toml file and ended up being confused for a few minutes until I found out what's wrong. With this change, clippy will suggest an existing field if there's one that's similar. ``` 1 | allow_mixed_uninlined_format_args = true | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: perhaps you meant: `allow-mixed-uninlined-format-args` ``` (in hindsight, the current behavior of printing all the config options makes it obvious in most cases but I still think a suggestion like this would be nice to have) I had to play around with the value a bit. A max distance of 5 seemed a bit too strong since it'd suggest changing `foobar` to `msrv`, which seemed odd, and 4 seemed just good enough to detect a typo of five underscores. changelog: when an invalid field in clippy.toml is found, suggest the closest existing one if one is found
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.