You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Philip,
Thanks for writing destructure_traitobject. I need your help understanding it.
I'm trying to pin down the warning I get about traitobject. I traced it to the crate log4rs, which I've used in my project. Log4rs depends on destructure_traitobject, and it seems that destructure_traitobject depends on traitobject.
Being that destructure_traitobject was written by you to fix the issues with traitobject, does this suggest that I can ignore the warning, and not worry about the future warning with respect to traitobject?
When Rust finally breaks from any contact with traitobject, how will destructure_traitobject continue to compile?
The text was updated successfully, but these errors were encountered:
Philip,
Thanks for writing destructure_traitobject. I need your help understanding it.
I'm trying to pin down the warning I get about traitobject. I traced it to the crate log4rs, which I've used in my project. Log4rs depends on destructure_traitobject, and it seems that destructure_traitobject depends on traitobject.
Being that destructure_traitobject was written by you to fix the issues with traitobject, does this suggest that I can ignore the warning, and not worry about the future warning with respect to traitobject?
When Rust finally breaks from any contact with traitobject, how will destructure_traitobject continue to compile?
The text was updated successfully, but these errors were encountered: