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
Rust considers all references dereferencable and hence adds the dereferencable attribute. This allows the compiler to insert spurious reads from that reference. There is currently no way around that.
Unfortunately, this means the approach implemented by this crate is currently flawed: the compiler may insert spurious reads from an &RO<T> (or any of the other types, including WO).
The UCG thread is probably the best place to discuss possible solutions to this problem.
(I am not sure if this issue should be reported against this crate or vcell.)
The text was updated successfully, but these errors were encountered:
Rust considers all references dereferencable and hence adds the
dereferencable
attribute. This allows the compiler to insert spurious reads from that reference. There is currently no way around that.Some more discussions for context:
Unfortunately, this means the approach implemented by this crate is currently flawed: the compiler may insert spurious reads from an
&RO<T>
(or any of the other types, includingWO
).The UCG thread is probably the best place to discuss possible solutions to this problem.
(I am not sure if this issue should be reported against this crate or
vcell
.)The text was updated successfully, but these errors were encountered: