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
The copy, copy_nonoverlapping and write_bytes methods are exposed both via core::ptr and std::ptr. In fact, std::ptr as just a re-export of core::ptr.
However, when comparing the two pages, core::ptr is missing a few items compared to std::ptr: copy, copy_nonoverlapping and write_bytes for some reason are not shown as "functions".
I just realized that thy are shown as "reexports". So likely I could have made rust-lang/nomicon#165 link to the versions in core::intrinsics instead. But we don't actually want people to use those paths, they are available on stable only due to a bug. We'd prefer if people used these symbols through ptr, but then it seems we have to link to std::ptr, which is somewhat annoying.
The text was updated successfully, but these errors were encountered:
The
copy
,copy_nonoverlapping
andwrite_bytes
methods are exposed both viacore::ptr
andstd::ptr
. In fact,std::ptr
as just a re-export ofcore::ptr
.However, when comparing the two pages,
core::ptr
is missing a few items compared tostd::ptr
:copy
,copy_nonoverlapping
andwrite_bytes
for some reason are not shown as "functions".I just realized that thy are shown as "reexports". So likely I could have made rust-lang/nomicon#165 link to the versions in
core::intrinsics
instead. But we don't actually want people to use those paths, they are available on stable only due to a bug. We'd prefer if people used these symbols throughptr
, but then it seems we have to link tostd::ptr
, which is somewhat annoying.The text was updated successfully, but these errors were encountered: