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
given we have a set of foundational crates depended on by practically the whole ecosystem (like https://github.com/rust-embedded/embedded-hal/), the risk of changes to these foundational crates causing large volumes of annoyance is pretty high.
it'd be awesome to have https://github.com/rust-lang/crater (or something like it) running over consumers of these crates so we can be informed of and mitigate the impacts of any necessary breakage.
i think just cross compilation (including the test suite), afaik the issues we're looking to avoid are all around types and interfaces so should be p much (where things can compile for a given target) target independent, and shouldn't require test running.
given we have a set of foundational crates depended on by practically the whole ecosystem (like https://github.com/rust-embedded/embedded-hal/), the risk of changes to these foundational crates causing large volumes of annoyance is pretty high.
it'd be awesome to have https://github.com/rust-lang/crater (or something like it) running over consumers of these crates so we can be informed of and mitigate the impacts of any necessary breakage.
possibly related to: #381
cc. @therealprof
The text was updated successfully, but these errors were encountered: