Hot Reload errors when not debugging?

Question

Building a solution in Visual Studio with one C++ syntax error now produces three error messages: one for the syntax error and two "Hot Reload" errors.

This started happening very recently. In fact, I was unfamiliar with Hot Reload until these errors started showing up a couple days ago.

Hot Reload sounds like a new form of edit-and-continue, (which I long ago disabled), so I would understand Hot Reload errors if I'd made a build-breaking edit while debugging.

Q: Why are Hot Reload errors reported when the program is not being debugged?

I'd expect Clean Solution to purge any cached state from build-to-build. Clearly that's wrong, since _Hot Reload errors are reported even when building immediately after Clean Solution.

The entire solution is C++ projects. Building x64 Release.

The errors are:

Failed to resolve section with contributions 0xA113DE82, 0x00000000, 0xC0100040, 0x00000092 (relocation #1 in section '[long mangled type name]).

Variable or function `[extremely long mangled function name]' was removed. Undeleted and undetected references could still exist.