watch this space
-

A weird MSVC error (C2666)
Consider a C++20 program that uses an overloaded == operator, such as the following. In == in main, MSVC gives us this error: Yes, the two alternatives that it tells us it “could be” are identical. What the heck? Clang gives us an infinitely better error (especially the last line): GCC does similar: As is
-

JetBrains forces “New UI”
Forcing of “New UI” prompts confusion and anger
-

PEXT and PDEP
A pair of neat x86 instructions.
-

CUPID and CPUID
Basically the same word.
-

Solving Advent of Code 2023 Day 10 Part 2
A solution.
