interlocked

Turned out we were using some implementation of shared pointers that used interlocked increment for incrementing the count but didn't use interlocked decrement for decrementing.

Log(value))]++; Maybe using Interlocked to become thread-safe and making the index calculation integers-only if this saves some cycles.

Reference counting incurs additional contention, due to interlocked increments/decrements and is also very hard to do properly.

Yup, the C# library is called Interlocked and it provides a variety of atomic operations.

Over time, mutations in those touching pieces interlocked more firmly until they resembled what we think of as gears.

There's been one accident at the US at a fully interlocked gate.

I find Interlocked absolutely essential for getting maximum performance -- like in implementing lock-free data structures.

Another would be break in interlocked loops, or clean failing when the software detect an hard failure and no memory can be used anymore.

And it turns out to be a tangle of interlocked gears.

Early ones had big levers, and early on, those were interlocked.

There's a solution available to prevent railroad crossing accidents, but it requires blocking the highway for much longer.[1] This is a fully interlocked grade crossing.

> Instead of writing clean, modular architecture, everything these days morphs into a huge mess of interlocked dependencies.

"Google has apps for pretty much all the most important functions on a phone or tablet — email, messaging, maps, storage, browsing, reading the news, finding and consuming media — and they are interlocked so that tasks flow naturally from one app to the next." Interlocked?

For C# users, I wrote about Interlocked.