Malachi
Malachi
### Is your feature request related to a problem? _No response_ ### Describe the solution you'd like. `idf.py create-project` and manually switching things to c++ isn't bad, but it sure...
### Answers checklist. - [x] I have read the documentation [ESP-IDF Programming Guide](https://docs.espressif.com/projects/esp-idf/en/latest/) and the issue is not addressed there. - [x] I have updated my IDF branch (master or...
Observed during `unity` `compile-only -e simavr` Feels like a pathing issue: ``` lib/estdlib/src/estd/internal/bip/../../ext/willemt/bipbuffer/bipbuffer.h:44:5: warning: type of 'bipbuf_offer' does not match original declaration [-Wlto-type-mismatch] int bipbuf_offer(bipbuf_t *me, const unsigned char *data,...
Our current deque operation is just a ring buffer. Useful but perhaps not correct Using these as a possible example, do a block style (pseudo ring) buffer: https://isocpp.org/blog/2023/09/inside-stl-the-deque-implementation-raymond-chen?utm_source=chatgpt.com https://devblogs.microsoft.com/oldnewthing/20230810-00/?p=108587&utm_source=chatgpt.com https://cpp-tip-of-the-day.blogspot.com/2013/11/how-is-stddeque-implemented.html?utm_source=chatgpt.com...
Since GCC supports the notion of c++17 constexpr global variables, upgrade `FEATURE_CPP_INLINE_VARIABLES` to reflect that. Note that GCC extension does NOT accept `inline` keyword, which appears to be an optional...
Add ability for something like: ``` layer2::istringstream in(s); string_view s2; s >> s2; ``` Since unlike `std` we are more comfortable sharing ownership of istringstream sourced buffer.
See if backporting this makes any sense https://en.cppreference.com/w/cpp/language/contracts.html Example use case https://en.cppreference.com/w/cpp/container/deque/pop_back.html
Would be convenient to have this in particular to support `rend` during a circular queue operation
Upgrade `layer1::deque` circular queue to use a burn-the-bool/burn-the-slot (sentinel) approach. In particular, the model where one queue slot is burned to know if we're full or empty. In doing so,...
Code works, but is super crusty. Rework: * Elevate usage of new `allocator_options` paradigm * With `handle_descriptor` and `handle_descriptor_base` * `single_fixedbuf_runtimesize_allocator::InitParam` ought to go * Consolidate `estd::internal::policy_base` and `allocator_options` *...