@strega-nil-ms If possible, I strongly recommend writing a Proposed Resolution for LWG-3788 if you want it to be accepted this decade - issues without Proposed Resolutions tend to linger for years, while those with simple and uncontroversial Proposed Resolutions can be quickly accepted within a meeting or two.

This seems to be somewhat more daring than we usually are for not-yet-accepted LWG issues (that change the Standardese 180 degrees, instead of merely clarifying something ambiguous). In the past, we've been burned by speculatively implementing "obviously correct" fixes that later turned out to be controversial (e.g. future's blocking destructor, IIRC).

That said, I think it's reasonable to be slightly daring here, as the existing self-move-assign behavior is so wacky, being a no-op is much more intuitive, and (importantly) this is a hopefully obscure case in relatively new machinery, so the possible impact is small.

✅ No modules impact.

Jonathan Wakely has put forward a resolution to this issue that the LWG mailing list seems happy about, which is in line with this implementation.

I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed.

I've pushed a merge with main to resolve a simple merge conflict with an updated WP citation in <thread> - this PR's change supersedes that.

Thanks for fixing this wacky behavior in both the Standard and our implementation! 😹 😸 🎉