Sends original data vs making a copy of data and sending it.
In meme context you’d be just making a copy of your consciousness and putting it in a machine. Whatever reason you’re doing it for - escape illness, survive armageddon, nothing changes for you. A copy of you lives on though.
I mean, just kill the host as soon as the upload is complete. at best you are not conscious during the process and when “you” wake up you are in the cloud. The version of you that awakes gets told that the “transfer” was complete.
Oh I know San junipero, just suggesting the plot of season 2 of future man as another similar reference - minds uploaded to “the cloud” and bodies destroyed on upload complete. Haley Joel Osmand is pretty decent as the antagonist of that season.
I guess you ask for C++. There Type* can be null while Type& can’t be null. When it gets compiled Type& is compiled (mostly) to the same machinecode as Type*.
Whats the difference between
void fn(Type& var)andvoid fn(Type* var)?Sends original data vs making a copy of data and sending it.
In meme context you’d be just making a copy of your consciousness and putting it in a machine. Whatever reason you’re doing it for - escape illness, survive armageddon, nothing changes for you. A copy of you lives on though.
It’s not like the post, secont is a pointer.
I mean, just kill the host as soon as the upload is complete. at best you are not conscious during the process and when “you” wake up you are in the cloud. The version of you that awakes gets told that the “transfer” was complete.
Upload is a fun show
I was thinking more along the lines of St. Junipero :D
Future man season 2?
Black Mirror
Oh I know San junipero, just suggesting the plot of season 2 of future man as another similar reference - minds uploaded to “the cloud” and bodies destroyed on upload complete. Haley Joel Osmand is pretty decent as the antagonist of that season.
never watched the show. Is it any good?
that’s a weird way to spell Pantheon.
I guess you ask for C++. There Type* can be null while Type& can’t be null. When it gets compiled Type& is compiled (mostly) to the same machinecode as Type*.
You can pass nullptr in the second example (that is not what OP wrote though, hes second is making a copy).
Thanks, I was Just curious. I knew what * did but I wasn’t sure about &