ObviousInRetrospect

There is another reason not mentioned here explicitly to do this. Some cores allow configuration tuning by define. As an example, https://github.com/SpenceKonde/DxCore/blob/master/megaavr/cores/dxcore/UART.h will accept SERIAL_RX_BUFFER_SIZE but today the only way...

this makes SerialUPDI hard to use as a programmer and generally may degrade the quality of other bug reports

so given the overhead of a callback function invocation from the ISR (are inline weak functions a thing?) what about some wrappers around the register manipulation + some examples for...

anything stuck where another set of eyes would be useful?

I was coming at this particular one from the angle of trolling through the issues to see if there was anything I might be able to help with and having...

hmm what about using preprocessor concatenation to cause a #error if they mismatch - either in a specific test sketch or in pins_arduino or something? [edit: not actually convinced this...

another path might be to change a pair of recipes in platform.txt and have one use the version and the other use {versionnum.major}.{versionnum.minor}.{versionnum.patch}{versionnum.postfix} to construct a path such that builds...

filed https://github.com/arduino/Arduino/issues/11813 but not optimistic and think if there isn't traction on fixing it by the release doing the less elegant thing is better for the users of the cores...

[#include ](https://songmeanings.com/songs/view/3530822107858967227/)

Is there any other information that would be helpful? Thanks.