Are waifus passed by reference or value?
>>51299861
hopefully by value, I rather have a copy than experiencing a race condition :3
>>51299861
I'd rather by value. I don't my waifu getting into other functions. If she's not with me she should be removed from the stack.
>>51300068
or worse, you might 'operate' on your waifu while other parallel functions is doing the same thing...
In real life they are passed by const reference.
All NEETs simply receive and view the one, and they collectively with their infinite free time are unable to even modify a single bit within that waifu.
>>51300011
>>51300068
Well, what are your arguments though?
On one hand, they are created by a person and therefore whenever we think of our waifus they're the same one that point to the original authors idea of who she is, on the other hand we could all as easily be just influenced by the original idea of the author and create our own copy of what they are in our minds, considering that how we see them is not necessarily the same as the original author sees them, we borrow the prototype but also build upon it with our own ideas.
>>51300131
That would be true if waifus had concrete existence, but they don't, because of that they are what we make them out to be in our minds, if we take the timeline of a manga or an anime
infinity <- 1 | 2 | 3 -> infinity
1.manga/anime doesn't exist
2. the idea is concieved and the characters created
3. manga/anime ends
then as soon as point 3 starts everything is up for interpretation, unless, you only view your waifu as she was in anime/manga e.g. you don't think of her as an entity outside of the world created by the original author AND restrict that world in your mind between point 1 and 3, only then she is a const reference, because only then there is no way of deviating from the original story.
>>51299861
It's probably exectly the opposite of what this guy said >>51300000
>>51300245
You have overlooked the fact that the function's equivalent is your desktop monitor. Where the arg of our waifu passed in is the monitor's output as a const signal. Therefore you do not have the privileges to modify the laws of physics and send back a response.
>>51300011
I'm glad I was born white so I don't have to live with a race condition.
>>51300321
>>51300321
That is true if you view a waifu as a pure set of coordinates for your computer to light pixels on a monitor which are supposed to emit light that should be received by your eye and then interpreted by your brain.
However if you see them as an abstract idea and the pixels that represent them as merely a medium that is supposed to transfer a base value for you to copy to your memory and then use as you wish, then it's not true.
well what value could a waifu have?
if X = waifu you could declare it to be anything however if your referencing it still holds its own value and is not you controlling it but it having a mind of it's own.
>>51300366
>>51300460
The original transmission remains as a const, your memory merely makes a local copy of the dereferenced value where you may choose to modify it to your heart's content, however the original const remains, belonging to it's origin, eternally, forever out of your reach.
>>51300614
Things that are out of my reach do not exist
>>51300656
Your brain is out of your reach. You can not touch it, not taste it, nor smell it, nor hear it, nor see it. Do you conclude your brain does not exist?
I rest my case.
>>51300855
I can see and touch my brain though.
>>51299861
fuck waifus
>>51299861
Dunno how they are passed, but they are returned as a union of structs.
>>51300131
>const
>implying you can't cast a const to non-const and overwrite it anyway
>>51299861
Reference, so i don't get anyone's sloppy seconds.
Waifu myWaifu = new Waifu();
>>51299861Waifu *holo = malloc(sizeof(Waifu));
function(holo);
>>51299861
They are clonned when passed somewhere.
>>51301695
They are stored in ROM
>>51300868
And you can see and "touch" the original const too, if you play around with pointers. However both would crash your system.
