Viewing profile — judofyr

In the initial state there's 24 (12 * 2) different possibilities: The marble you're looking for is one of 12 and it's either lighter or heavier. By using a balance scale there's 3 …

I imagined that I'm 24 years old and I have a 20 years old brother. When I were his age, he would have been 16 years old. I also realized that this can be expressed in terms of a t…

Rephrasing it makes it easier to grasp: Mary is 24 years old. When Mary was Ann’s current age, Ann was 12 years old (half Mary’s current age). This makes it a bit easier to realize…

Some examples just from the second paragraph: - while none of this is exaggerated - it comes down to a real design choice - the bloat, the amplified writes, the vacuum babysitting …

Not sure where I picked up this, but I’ve added this to my global Git ignore: attic That way you can just create an attic directory in any project where you can keep random stuff t…

Ignoring the misuse of epsilon, I'd also say that you'd be helping your users more by not providing a general `assert_f64_eq` macro, but rather force the user to decide the error m…

This is just wrong. See https://en.cppreference.com/w/cpp/atomic/memory_order.html . Emphasis mine: > A store operation with this memory order performs the release operation: no re…

It’s just an encrypted file on disk. You’d depend on whatever backup solution you already have in place.

Very cool project! Always happy to see more work around static analysis. However, looking at the recent commits it doesn't quite look like the most solid foundation: https://github…

Can you show an actual minimal C program which has this problem? I’m trying to follow along here, but it’s very hard for me to understand the exact scenario you’re talking about.

Is there a specific reason to store the key + value as an `uint64_t` instead of just using a struct like this? struct slot { uint32_t key; uint32_t value; }

> If a carpenter shows up to put a roof yet their hammer or nail-gun can't actually put in nails, who'd you blame; the tool, the toolmaker or the carpenter? I would be unhappy with…

I think this is a bit unfair. The carpenters are (1) living in world where there’s an extreme focus on delivering as quicklyas possible, (2) being presented with a tool which is pr…

I’m sorry, but this is such a terribly unscientific approach. You want to make a case for your hypothesis? Follow a structured approach with real arguments. Saying «I know that cor…

Maybe I explained it a bit imprecise. I was trying to explain the following behavior: def foo p 1 yield p 2 end foo { break } This only prints "1" because the break stops the execu…

Blocks are fundamentally different from functions due to the control flow: `return` inside a block will return the outer method, not the block. `break` stops the whole method that …

> This has massive implications. SEC means low latency, because nodes don't need to coordinate to handle reads and writes. It means incredible fault tolerance - every single node i…

> The standardized location is Library. Except for Zsh (~/.zshrc), SSH (~/.ssh/config), Vim (~/.vimrc), Curl (~/.curlrc), Git (~/.gitconfig). Apple could have chosen to patch these…

> Suggest contrary to that is wrongthink and enough to have one ostracized not only from science, but also society as a whole. There's many scientists who have published the "contr…

Your first link (Wikipedia) directly contradicts your examples: > Although IQ differences between individuals have been shown to have a large hereditary component, it does not foll…

No, sorry. I was just remembering where I've typically seen sequential consistency being used. For instance, Peterson's algorithm was what I had in mind. Spinlock is indeed a good …

A mutex would be the most trivial example. I don't believe that is possible to implement, in the general case, with only acquire-release. Sequential consistency mostly become relev…

Acquire-release ordering provides ordering guarantees for all memory operations. If an acquire observes a releases, the thread is also guaranteed to see all the previous writes don…

Here's a few workflows that I really enjoy in jj: - While I'm working on something I can do `jj desc` and start writing the commit message. Every edit is automatically being added …

This is one the reasons I find it so silly when people disregard Zig «because it’s just another memory unsafe language»: There’s plenty of innovation within Zig, especially related…