-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[beta] Give a better error message for unknown derive messages #39444
Conversation
b1e5cbf
to
17605a1
Compare
As a note to reviewers on this PR, we're not able to use @bors to approve branches going to beta, and it's in fact highly recommended to do so! (just to avoid hitting the merge button) |
You wrote (emphasis mine):
Did you mean: "we're NOW able"? |
Ooops, yes! To clarify @bors should be used to approve this PRTo be fair the "t" and "w" keys are ... not at all close to each other. |
I'm a bit confused, what is this a backport of? And which beta does it have to land in? |
On 1.15, the code |
@bors r+ |
📌 Commit c3f9075 has been approved by |
@bors: p=1 (PR against beta branch) |
⌛ Testing commit c3f9075 with merge 8fc0085... |
💔 Test failed - status-travis |
It might be prudent to wait still for patches to land on master before letting bors try to land them on beta, in case there are problems with the patch. |
@bors r=jseyfried |
📌 Commit 6519e8b has been approved by |
[beta] Give a better error message for unknown derive messages This PR improves the error message for unknown derive macros. Currently unknown derives give the following error, which is very misleading: ``` `#[derive]` for custom traits is not stable enough for use. It is deprecated and will be removed in v1.15 (see issue #29644) ``` I'm currently working on a PR that will change this (#39442) to the following: ``` cannot find derive macro `Foo` in this scope ``` This PR backports the (as yet unmerged) error message to beta/1.16 (it's a pity that this is probably too late for 1.15). r? @jseyfried
☀️ Test successful - status-appveyor, status-travis |
This PR improves the error message for unknown derive macros.
Currently unknown derives give the following error, which is very misleading:
I'm currently working on a PR that will change this (#39442) to the following:
This PR backports the (as yet unmerged) error message to beta/1.16 (it's a pity that this is probably too late for 1.15).
r? @jseyfried