https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114990
Nathaniel Shead <nshead at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
CC| |nshead at gcc dot gnu.org
--- Comment #20 from Nathaniel Shead <nshead at gcc dot gnu.org> ---
I'll close as a dup of PR99000 then for the include/import ordering. Thanks
for the report!
(In reply to Larry Smith from comment #19)
> Op here, finally got around to reviewing comment #1 (well over a year
> later). Yes, it's an ordering issue. Rearranging things so that all
> #includes come before imports fixes it. Hopefully will be corrected at some
> point (clearly low priority). @Patrick: Thanks for your help (appreciated).
And yeah, unfortunately getting includes after imports working well enough
currently looks very tricky, so I'm just ignoring it and focussing on lower
hanging fruit in the meantime. Unless someone else picks it up I don't imagine
it'll be fixed for GCC16, but maybe GCC17? :D
*** This bug has been marked as a duplicate of bug 99000 ***
