@yugaego Except every move (or Copy-type assignment) isn't necessarily a copy! And "initialized"/"uninitialized" are lousy terms to use here; after a move, the source binding is certainly invalid (and the compiler rightly goes out of her way to prohibit its use), but those bytes aren't "uninitialized" (especially if the copy has been optimized away--although I wouldn't even call that an optimization so much as the semantics of the language).
=> More informations about this toot | View the thread | More toots from d2718@hachyderm.io
=> View yugaego@fosstodon.org profile
text/gemini
This content has been proxied by September (3851b).