« first day (392 days earlier)      last day (183 days later) » 

13:10
0
Q: What are the approaches of protecting against partially initialized objects?

user23013Usually the programmer is responsible for not leaving partially initialized objects in unwanted places and calling them in unwanted ways. But like Rust has "ownership" and "lifetime" to protect against invalid pointer accesses, are there ways to protect against misusing partially initialized obje...

13:24
0
Q: What are the approaches of protecting against partially initialized objects?

user23013Usually the programmer is responsible for not leaving partially initialized objects in unwanted places and calling them in unwanted ways. But like Rust has "ownership" and "lifetime" to protect against invalid pointer accesses, are there ways to protect against misusing partially initialized obje...

0
Q: What are the approaches of protecting against partially initialized objects?

user23013Usually the programmer is responsible for not leaving partially initialized objects in unwanted places and calling them in unwanted ways. But like Rust has "ownership" and "lifetime" to protect against invalid pointer accesses, are there ways to protect against misusing partially initialized obje...

13:55
Those all have the same post ID
whose bot is that? @lyxal, @Ginger, or -- I can't seem to ping Rydwolf here
it's rydwolf's
@RydwolfPrograms why is your bot being a silly
until he responds I'm leaving the three messages here
14:32
lyxal doesn't do bots
Beepn't boopn't
15:13
Interesting, this is the second report I've had of general silliness
ooh that's recent enough it's likely still in the logs
I see what's happening
Ugh, this is gonna be a pain to fix, I gotta go to work but once I'm back I'll take a look
Basically it's panicking during one request or another, so there's probably some issues with cloudflare or something
 
2 hours later…
16:56
0
Q: Compressed pointers, why not "relative" rather than "base" encoding?

Compl YueJava has compressed oops, NodeJS has compressed pointers, they all use a common "base" address to encode/decode pointer values. There is an obvious downside: total heap size get rather limited. As compressed pointers are stored in RAM, why not use a narrow (e.g. 32-bit) offset, relative to its ow...

 
6 hours later…
23:09
Can anyone make sense of this answer? It seems half ungrammatical, the other half grammatical but hard to parse. langdev.stackexchange.com/a/3864/89
I was wondering how that answer made its way into my inbox until I realised that it's on a question I asked :p
Thought it was some moderation thing
@kaya3 "what do you do on a regular iteration of a for loop? How do you get back to the first instruction? (More specifically, how do you get back to the condition check?) Wouldn't you usually store the memory address of the instruction so you can jump to it? Therefore a continue is just a jump to that memory address. Same thing with a break, except at the end"
Which would be good if I was asking about a compiled language
23:35
@kaya3 I think this looks like a comment. Like, someone who thinks SO is a forum
very train of thought
with some esl spice peppered in
english as a second language
the train of thought doesn't seem like what a native speaker would vomit out and stuff like "how do" feels like it's common with learners
23:38
Maybe the right kind of person could be able to identify the first language based on such clues.
I think the first language here is German
ah, but that's cheating :-)
i was about to say "smh could be swabian" until i remembered swabian is still just a dialect of high german
The goal was also to get insight on what he means based on knowledge of that first language, so, looking at the profile doesn't help that much with that.

« first day (392 days earlier)      last day (183 days later) »