Update tracking issue for const_caller_location #76157
Merged
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
LeSeulArtichaut
added
the
S-waiting-on-review
|
Seems like @rust-highfive skipped this, so r? @joshtriplett for re-assignment/approval. |
|
@bors r+ rollup |
|
📌 Commit 8142457 has been approved by |
bors
added
S-waiting-on-bors
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Sep 5, 2020
…racking_issue, r=joshtriplett Update tracking issue for const_caller_location Update the tracking issue to rust-lang#76156, as suggested in rust-lang#76105.
Dylan-DPC-zz
pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Sep 6, 2020
…racking_issue, r=joshtriplett Update tracking issue for const_caller_location Update the tracking issue to rust-lang#76156, as suggested in rust-lang#76105.
|
☀️ Test successful - checks-actions, checks-azure |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Update the tracking issue to #76156, as suggested in #76105.