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
Since we renamed LayoutVerified to Ref in #203, we should add a type alias to help ease the transition to 0.7.0. This alias should be marked as #[deprecated] to nudge users in the right direction.
It's also possible that we could use this approach (albeit without the #[deprecated] annotation) to backport the rename to 0.6.x (see #215). Without the deprecation warning, it's unlikely that many people would switch to Ref - the main benefit would be to make future cherry-picks less likely to result in conflights (#203 was a large change that affected many lines of code). We would need to be very careful to ensure that the type alias is genuinely a backwards-compatible standin for the struct itself.
The text was updated successfully, but these errors were encountered:
This should help make the transition to 0.7.0 easier, as code which
currently uses `LayoutVerified` will get a deprecation warning instead
of a (much less helpful) "not found" error.
Closes#221
Since we renamed
LayoutVerified
toRef
in #203, we should add a type alias to help ease the transition to 0.7.0. This alias should be marked as#[deprecated]
to nudge users in the right direction.It's also possible that we could use this approach (albeit without the
#[deprecated]
annotation) to backport the rename to 0.6.x (see #215). Without the deprecation warning, it's unlikely that many people would switch toRef
- the main benefit would be to make future cherry-picks less likely to result in conflights (#203 was a large change that affected many lines of code). We would need to be very careful to ensure that the type alias is genuinely a backwards-compatible standin for the struct itself.The text was updated successfully, but these errors were encountered: