John Wellbelove

Unfortunately, many type traits are next to impossible for the ETL to reverse engineer due to the reliance on the compiler's 'insider knowledge'. The only way to use your fix...

I added the `ETL_ASSERT_OR_RETURN_VALUE` and related macros so that there was an option for the application to continue or terminate after logging the error in the error handler. You are...

`ETL_NO_CHECKS` overrides every other error handler directive. If defined then every `ETL_ASSERT_xxx` will be a NOP. `ETL_NO_CHECKS` is for the scenario where the coder is looking to extract the absolute...

Fixed 20.38.11

_For what I saw having a templated base class as for `etl::message` won't work with the pre-C++17 implementation_ Did you mean `etl::message_router`?

Were you getting warning from the compiler?

Did you get errors or warnings about 'missing initializers'? `left_spec` & `right_spec` have default constructors, so they shouldn't need explicit initialisation.

I'm not sure why the template function `value()` is being instantiated when the compiler has absolutely no idea what the requested return type actually might be! Where exactly is `T`...

Ah yes, I see. The error only mentioned `value()`. I forgot about those other member functions. Adding `enable_if` would be pretty simple to add; I may add it while I'm...

Actually, a `static_assert` would be easier than `enable_if`. (Though it wouldn't solve your problem) Also, to address the code size issues, I'm thinking of mandating that the element type **must**...