It's common to use fixed magic numbers for things like allocation headers/footers to detect write-clobbering corruption but you can actually do one better with incrementally updatable checksums at a very manageable cost. An intentional field write removes the checksum contribution corresponding to its old value before writing the new value and then it adds in the checksum contribution corresponding to the new value. There's an obvious concurrency issue here, so reason and apply accordingly.
@80f08b97 It seems like a certainty that there's going to be open-and-shut cases of copyright violation. But unless some sort of massive class action succeeds, yeah, it's probably going to be more than worth it for Microsoft to just take it on the chin in those cases.
@80f08b97 "We are sensitive to the concerns of authors, and we believe that Microsoft rather than our customers should assume the responsibility to address them." We are so sensitive to author's rights that we are going to use our legal muscle to crush any authors who may find that their works have been plagiarized via Copilot laundering.
Oddbean new post about login | logout
Notes by a297d2ef | export