Clarify that the expected runtime symbols signature is for the current target only#159902
Open
Urgau wants to merge 1 commit into
Open
Clarify that the expected runtime symbols signature is for the current target only#159902Urgau wants to merge 1 commit into
Urgau wants to merge 1 commit into
Conversation
rustbot
added
S-waiting-on-review
GuillaumeGomez
approved these changes
Jul 25, 2026
Member
|
Looks good to me, thanks! r=me once CI pass |
Member
Author
|
@bors r=GuillaumeGomez rollup |
Contributor
rust-bors
Bot
added
S-waiting-on-bors
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Jul 25, 2026
…target, r=GuillaumeGomez Clarify that the expected runtime symbols signature is for the current target only Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (`i8` vs `u8`), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic. So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target. r? @GuillaumeGomez
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Jul 25, 2026
…target, r=GuillaumeGomez Clarify that the expected runtime symbols signature is for the current target only Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (`i8` vs `u8`), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic. So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target. r? @GuillaumeGomez
chenyukang
added a commit
to chenyukang/rust
that referenced
this pull request
Jul 26, 2026
…target, r=GuillaumeGomez Clarify that the expected runtime symbols signature is for the current target only Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (`i8` vs `u8`), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic. So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target. r? @GuillaumeGomez
chenyukang
added a commit
to chenyukang/rust
that referenced
this pull request
Jul 26, 2026
…target, r=GuillaumeGomez Clarify that the expected runtime symbols signature is for the current target only Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (`i8` vs `u8`), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic. So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target. r? @GuillaumeGomez
chenyukang
added a commit
to chenyukang/rust
that referenced
this pull request
Jul 26, 2026
…target, r=GuillaumeGomez Clarify that the expected runtime symbols signature is for the current target only Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (`i8` vs `u8`), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic. So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target. r? @GuillaumeGomez
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Jul 26, 2026
…target, r=GuillaumeGomez Clarify that the expected runtime symbols signature is for the current target only Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (`i8` vs `u8`), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic. So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target. r? @GuillaumeGomez
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
3 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.
Some of the signatures expected by our runtime symbols are slightly different from one target to the other one (
i8vsu8), and while the original definition uses type alias, they are not recorded and displayed in the diagnostic.So, to avoid any ambiguity let's add a small note that the displayed signature is only for the current target.
r? @GuillaumeGomez