https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39478
--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Daniel Frey from comment #3) > instead. I'd still like to see GCC to hint at the loop when trying to > complete types where the completion of A requires a completed B and the > completion of B requires a completed A. Then, what output do you propose for the testcase above? I'm not even sure GCC knows there is cycle. It probably only knows that the type is not complete at a time where the standard says it should be complete, and it doesn't try to figure out why it is not.
