-
Notifications
You must be signed in to change notification settings - Fork 116
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
Relax Debug bounds on IpcReceiver and IpcSender #88
Comments
I think the actual problem is that for some reason deriving Debug on something with |
No that's only because we derive their implementation, we don't need the bound if we implement it ourselves. |
@nox yes -- my point was that I don't see why the derived implementation has to impose these bounds, if a custom implementation doing exactly the same doesn't need it... Unless the derived implementation actually does something else that I'm missing? Otherwise I consider it a shortcoming in Rust, that should be fixed rather than working around it. |
@antrik It's not really fixable easily in Rust, so we work around it here, nothing too surprising. It's hard for rustc to know which bounds to use for which types. |
I think a recent nightly does it better, but that means that stable won't derive the same thing for now AFAIK. |
Their
Debug
impls shouldn't requireT: Debug
.The text was updated successfully, but these errors were encountered: