* Add docs and tutorial for etl::intrusive_avl_tree (#1608)
* Add docs and tutorial for etl::intrusive_avl_tree
Documents the intrusive AVL tree added in PR #1425: a full API reference
page under Containers/Trees, and a tutorial demonstrating ordered access
to intrusively-linked objects with unpredictable lifetimes, including
move support and destructor-driven automatic removal from the tree.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Add complexity shortcode and document its usage
Introduces a {{< complexity >}} Hugo shortcode (with light/dark styling
for constant/logarithmic/linear/linearithmic/polynomial/exponential
classes) for rendering Big-O complexity inline, applies it throughout
the intrusive_avl_tree API reference in place of raw "O(...)" text, and
documents the Description/Complexity structure and supported classes in
DOCUMENTATION.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Fix issues found by @CodeRabbit
* Put complexity notes on their own lines in intrusive_avl_tree docs
Move the complexity shortcode from the inline "**Complexity:**" label
to its own line under a "**Complexity**" label. Notes that give several
alternatives (e.g. amortized vs. worst-case) now show each one on a
separate line. Update the guideline in DOCUMENTATION.md to match.
* Update complexity examples in DOCUMENTATION.md
Add the hard line break after the "**Complexity**" label in the
example, and rewrite the list of supported complexity classes in the
new two-line format, including an example with several alternatives.
* Add logarithmic complexity example to DOCUMENTATION.md
---------
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
* Updated sponsors pages
* Refactor the documentation css to group styles for light and dark themes
* Update Codacy badge in README.md
Updated Codacy badge link to reflect new project status.
* Fix Codacy badge display
* refresh codacy integration status
* Expose more Zephyr Kconfigs for error handling (#1622)
* zephyr: make `ETL_DEBUG` default to on if Zephyr assertions are enabled
this is the more appropriate default: ETL_DEBUG controls some container assertions, so it should follow the Zephyr assertions by default
* zephyr: expose new error-checking configs
* zephyr: add Kconfig choices for error handling
* Fix find and rfind position handling in string and string_view
* Default the rfind string_view position to npos
The string_view overload defaulted pos to 0, so rfind(view) only found
a match at the start of the string. The other rfind overloads and
std::basic_string use npos.
---------
Co-authored-by: Sergei <sergej.shirokov@gmail.com>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: John Wellbelove <jwellbelove@users.noreply.github.com>
Co-authored-by: John Wellbelove <john.wellbelove@etlcpp.com>
Co-authored-by: Eden Frosst <edenfrosst@gmail.com>
zephyr_link_interface() does not work as intended because the
implementation in zephyr/cmake/modules/extensions.cmake:
function(zephyr_link_interface interface)
target_link_libraries(${interface} INTERFACE zephyr_interface)
endfunction()
is backwards, i.e., target_link_libraries(etl INTERFACE zephyr_interface)
vs. target_link_libraries(zephyr_interface INTERFACE etl).
The workaround results in the following CMake code being executed:
target_link_libraries(zephyr_interface INTERFACE etl::etl)
* Add Zephyr build system module.yml (#1074)
The Zephyr build system requires that modules have a `module.yml` file to specify where the module cmake and kconfig files are located.
These can also be explicitly set as "external" meaning that they do not exist within the module tree, itself. These build file can still be specified elsewhere via cmake variables, explained more in-depth here: https://docs.zephyrproject.org/latest/develop/modules.html#modules-module-ext-root
This change makes it such that ETL can be included more easily in zephyr projects running on embedded systems. A similar change can be observed in the public nanopb repository, where the repo only requires its own `zephyr/module.yml` file to be found by the zephyr build system, but the kconfig and cmake additions can exist outside of the library repository.
* Support const pointers to etl::is_aligned()
---------
Co-authored-by: Zach Van Camp <marshmilo100@gmail.com>
This will allow ETL to be included via west in a zephyr build without any additional wrappers or external kconfigs.
Signed-off-by: Zach Van Camp <zach.vancamp@etcconnect.com>
Co-authored-by: Zach Van Camp <zach.vancamp@etcconnect.com>
# Conflicts:
# zephyr/module.yml
