https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95917
--- Comment #6 from fdlbxtqi <euloanty at live dot com> --- (In reply to Iain Sandoe from comment #4) > (In reply to fdlbxtqi from comment #3) > > Jonathan. I am MAD at you. This is absolutely your fault. I told you to > > always write inline and you guys do not then allow Herb Sutter to ban me. > > Here is the fault in your own controlled codebase. Are you satisfied? > > > > https://github.com/isocpp/CppCoreGuidelines/issues/1630 > > > > YES! INLINE ALL YOUR FUNCTIONS. AVOID function pointers and virtual > > functions as plagues. > > 1. jonathan did not write this header - I did, > 2. we all make mistakes, shouting at folks isn't the optimum way to get them > fixed > 3. this bloat can only occur IF you include a header you are NOT using. > > i.e. > #include <coroutine> > in a source that has no coroutines. Iain, you did a great job on implementing coroutines. I am here to show the examples. https://github.com/expnkx/fast_io/blob/master/testsuites/0005.freestanding/0002.println/helloworld_linux.cc https://github.com/expnkx/fast_io/blob/master/testsuites/0005.freestanding/0002.println/helloworld_linux.s https://github.com/expnkx/fast_io/blob/master/testsuites/0005.freestanding/0002.println/helloworld_linux_writev.cc https://github.com/expnkx/fast_io/blob/master/testsuites/0005.freestanding/0002.println/helloworld_linux_writev.s Of course, I disabled exceptions and RTTI. I can compile this on one computer and fail on another since it introduced libsupc++ again with std:: bad_alloc, global new for examples. This is serious if people are using C++ for making operating systems.
