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
We take in and pass out several different types; types which should have very clear trait bounds that allow us some future iteration without breaking semver too.
In general the last point implies that we should have more specific requirements for types that are passed to us and guarantee much less traits for types we pass out.
This issue is especially relevant for auto-traits (Send, Sync, Unpin, UnwindSafe, …) that can easily be accidentally removed and then constitute a hidden breaking semver change.
The text was updated successfully, but these errors were encountered:
We take in and pass out several different types; types which should have very clear trait bounds that allow us some future iteration without breaking semver too.
In general the last point implies that we should have more specific requirements for types that are passed to us and guarantee much less traits for types we pass out.
This issue is especially relevant for auto-traits (
Send
,Sync
,Unpin
,UnwindSafe
, …) that can easily be accidentally removed and then constitute a hidden breaking semver change.The text was updated successfully, but these errors were encountered: