libCat VS Kalman

I recently implemented a runtime for `__builtin_cpu_init()`, `__builtin_cpu_supports()`, and `__builtin_cpu_is()` for x86-64. Using these compiler intrinsics, or a higher level feature such as `[[gnu::cpu_dispatch]]`, you can write functions that behave differently on different CPUs. Fortunately the implementation isn't terribly complex. On x86, it's based around a neat `cpuid` instruction, and other ISAs have similar features.

https://github.com/Cons-Cat/libCat/blob/main/src%2Flibraries...

That's awesome! I'm working on something that sounds similar. https://github.com/cons-cat/libcat

I'd love to see your work if you're willing to share it here!

This runtime size bothers me a lot. So much that I've been working on a new runtime for C++ that breaks POSIX compatibility to keep binaries as small as they can be. The hello world with LTO is 330ish bytes right now, and I think that can get smaller. https://github.com/Cons-Cat/libCat

I'm working on a library that replaces both C++ and C/POSIX standard libraries (https://github.com/Cons-Cat/libCat), but even then I need to define a few std:: namespace symbols for some features. In the case of std::initializer_list, my answer is just don't use that feature, because you don't really need it.

It's worse in the standard library than it has to be. When I refactored my traits to minimize template instantiations and lean on concepts as much as possible, I measured over 30% improvement to clean build compile times. It's not possible for the standard to do this, because it would subtly change the API. For instance, you can't instantiate or take the address of a concept, but you can for a type-trait class. No reason you'd want to do that, but you can, so they can't "break" the standard library by optimizing this.

This doesn't have to be true. Over the past year I've made progress towards demonstrating how even non-freestanding C++ can be written without any C or C++ standard library headers or DLLs (with large benefits). There are a few names which the compilers require to be in the std:: namespace, though, but they're very special features like source_location and construct_at with semantics that can't be expressed otherwise.

This bit cast has no overhead in debug mode, and is a little bit more generally useful than std::bit_cast(), but cannot be constant evaluated. https://github.com/Cons-Cat/libCat/blob/main/src/libraries/utility/implementations/bit_cast.tpp

It isn't that hard to put a predicate into a type. We have lambdas in an unevaluated context, CTAD, and templated type aliases. https://github.com/Cons-Cat/libCat/blob/main/src/libraries/scaredy/cat/scaredy https://github.com/Cons-Cat/libCat/blob/main/src/global_includes.hpp#L70 https://github.com/Cons-Cat/libCat/blob/main/src/libraries/linux/cat/linux#L289 You do it like this.

But suppose that you have code with no standard library calls at all. Would it still make sense to choose this naming convention? This is actually possible, with a few special exceptions. GCC requires that an implementation of std::source_location has very particular class member names, GCC assigns special semantics to a few function names including std::construct_at and std::move (people seem to know it's inlined, but did you know std::move is required for move-related warnings?), and most intrusively of all, a promise_type must be snake_case. Other names can be worked around by using them into a different namespace with a different letter-case, but promise_type seems unavoidable.

Since you mentioned C++ and Kalman filters, I author this Kalman filter library which helped me to get reacquainted to control theory, tries to be approachable, and lists a variety of sources to ease in the topic with examples.

Yes, and here's one for sanitizers. Other tools, documentation, and coverage in the neigbhorong files.

I've been learning FectContent as well with some successes and failures.

My goal with this Kalman filter for C++ is to solve your exact question.

I released a first version of a generic Kalman filter.

I use fmt and others in my project with CMake fetch and it's been a good experience so far: fetch, declare, link in a few lines. Hope this can be useful to someome.

Gratuitous French codebase self-promotion though. /s

Would you be open to exploring an implementation collaboration? I author a C++ Kalman library and would like to expand demonstrators.

A façade (example) included only for your GCC builds and with the fmt library would allow you to generically use the std::format support in your code. Avoiding the fmt:: and dependencies with MSVC. When the support lands in GCC, only that file would need to be deleted.

I use it with boilerplate similar to this: https://github.com/FrancoisCarouge/Kalman/blob/develop/benchmark/benchmark.cpp and run the executables with priority and pining: nice -n 20 tasker -- cpu-list 0