emit errors during AbstractConst building #76939
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
rust-highfive
added
the
S-waiting-on-review
Yea, without emitting errors on failing to build an abstract const we'd just be pushing function author problems onto function users. This PR makes sense though we really need to build good diagnostics here, as this will be a big pain point. Ideally we could suggest a function to call instead if there's one with a matching body, but that's gonna be horrible to figure out. |
lcnr
changed the title
|
While the error messages are still quite bad, this seems like a good first step to me and we can improve them as we go. Marking as ready for review |
oli-obk
reviewed
Sep 21, 2020
oli-obk
reviewed
Sep 21, 2020
|
@bors r+ |
|
馃搶 Commit 2f893e4 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 22, 2020
emit errors during AbstractConst building There changes are currently still untested, so I don't expect this to pass CI 馃槅 It seems to me like this is the direction we want to go in, though we didn't have too much of a discussion about this. r? @oli-obk
ecstatic-morse
added a commit
to ecstatic-morse/rust
that referenced
this pull request
Sep 22, 2020
emit errors during AbstractConst building There changes are currently still untested, so I don't expect this to pass CI 馃槅 It seems to me like this is the direction we want to go in, though we didn't have too much of a discussion about this. r? @oli-obk
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Sep 23, 2020
Rollup of 9 pull requests Successful merges: - rust-lang#76898 (Record `tcx.def_span` instead of `item.span` in crate metadata) - rust-lang#76939 (emit errors during AbstractConst building) - rust-lang#76965 (Add cfg(target_has_atomic_equal_alignment) and use it for Atomic::from_mut.) - rust-lang#76993 (Changing the alloc() to accept &self instead of &mut self) - rust-lang#76994 (fix small typo in docs and comments) - rust-lang#77017 (Add missing examples on Vec iter types) - rust-lang#77042 (Improve documentation for ToSocketAddrs) - rust-lang#77047 (Miri: more informative deallocation error messages) - rust-lang#77055 (Add #[track_caller] to more panicking Cell functions) Failed merges: r? `@ghost`
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.
There changes are currently still untested, so I don't expect this to pass CI 馃槅
It seems to me like this is the direction we want to go in, though we didn't have too much of a discussion about this.
r? @oli-obk