Event JSON
{
"id": "1abc4a103b34d7e3d37988b7810ba70def2952ddcf7864362a53f8ae2c7d88ea",
"pubkey": "a30213f4585ec4fd1c68cfeb382947b44f290af9a0853842a497b7e5ef2242e9",
"created_at": 1709992579,
"kind": 1,
"tags": [
[
"p",
"7504af51f1ff5739007788ce4f6384033bafca5c35538db545352e64b1366ebe",
"wss://relay.mostr.pub"
],
[
"p",
"70d49fcb2c041ce0f4f47cae43cb0ae4b0ea4a2d4ac96719f46d7adb080e58c7",
"wss://relay.mostr.pub"
],
[
"e",
"701abc6b238d607c8d1477d258314c920262b0089d0c7741c605963a4c8ddb80",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/wosrediinanatour/statuses/112066073703817313",
"activitypub"
]
],
"content": "nostr:npub1w5z27503latnjqrh3r8y7cuyqva6ljjux4fcmd29x5hxfvfkd6lq88rl8t Roughly, std::move cast to rvalue reference. Then, instead of a copy constructor*, a move constructor* is used, which often does what is called \"shadowed copying\" in C. The copy constructor of a unique_ptr is deleted.\n\nMoved-from objects are valid objects, but everything else is undefined and depends on implementation and optimization of the compiler. So, a smart pointer like unique_ptr could wrap a nullptr in theory, but most probably does not. \n\n* or assignment operator",
"sig": "3faef3032dc76ccc898b090eb5eb47b036f271cb5ba891305a93c519b01de92391168de7fa223126965af47a10b50c185c689c71f1201646e210a32718302b8b"
}