Dirk O. Kaar

@mcspr This release 8.1.0 is ready for ESP32 IDF 5.1 and fixes a few other compilation problems as well. Please merge at your discretion.

Some careful consideration by the core team is required here: the new ghostl library apparently does get pulled in just fine by the Arduino library dependency framework, but this is...

"Bundling" like previously, or are you suggesting something I haven't thought of? Anyway: ``` libraries/esp8266/examples/SerialStress/SerialStress.ino libraries/ESP8266WiFi/examples/WiFiTelnetToSerial/WiFiTelnetToSerial.ino libraries/lwIP_PPP/examples/PPPServer/PPPServer.ino ``` are the only place where the EspSoftwareSerial lib is used directly. My...

I've checked the aforementioned sketches. The all appear to use EspSoftwareSerial in order to have two UARTs available, one for logging. IIRC the second UART of ESP8266 is TX only,...

I don't understand, going backward to `#include ` and including ghostl as a copy in EspSoftwareSerial is not an option now - just to state it categorically once more. Especially...

Ah, CI, right. Would you consider adding this to the default? I'm currently using a platform.local.txt: ``` build.stdcpp_level=-std=gnu++20 compiler.cpp.extra_flags=-fcoroutines -std=gnu++20 ```

About translating c++ namespace into directory stucture ... good point... I'm working that out. Bear with me.

@d-a-v I'm beginning to wonder if the test methodology is off target: we are going the extra mile to extract a good delay duration - that is what this PR...

@d-a-v unfortunately I have to focus my attention on other projects. While I think there's still something strange about using gcd, my current proposal has a significant performance impact and...