-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Poor error message when a subtype is not Sync as required #20965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Changing the recursion limit here does not appear to help, nor does the workaround @nikomatsakis suggested for #19318 (I attempted to use it on the CanvasMsg type, but there was no change in the output). |
So, whats the error here? There is no mention of |
How is the compiler right? Senders should always be able to be sent bare without needing to be wrapped in |
It's not clear to me how removing the |
@jdm senders can be sent yes, but the compiler isn't complaining about I'm not sure where you got the idea this had anything to do with |
Ah, I see. I appreciate the explanation; I got caught up in the superficial similarity to #19318. |
Let's morph this to cover the terrible error message, in that case. |
Then again, a smaller testcase using a more recent version of rustc gives me:
|
(@jdm so I infer you are satisfied with that error message? We did put some effort into making these problems more diagnosable) |
Yes, the newer error messages give a much more sensible chain of cause and effect. |
If you change https://github.com/servo/servo/blob/81f47344d6e121d86de368a25107415406de3c0f/components/layout/fragment.rs#L227 to read
Option<Sender<CanvasMsg>>
, trying to build Servo produces a ton of confusing error messages:The text was updated successfully, but these errors were encountered: