Borislav Stanimirov

`object::clear_mixin_data` is `noexcept`, but relies on an `noexcept(false)` destructor. It should never throw in the given case, but still the compiler will generate calls to `std::terminate` there. It is possible...

`domain::get_type` copies the original query indiscriminately even though if no mutation rules change it, it itself can be used for the query storage. No rule touching a query is expected...

A list of enhancements which can be done for empty (zero-size) mixins: * All empty mixins can share the same part of the object mixin buffer * Empty external with...

Demo of mutating objects in multiple threads while calling messages on them

This is a list for a more distant future, but there are concrete ideas for then * Zig * Lua * JS (+ wasm)

Not sure what to use yet

* Two domains * Shared libs * Idiomatic separation * ... ?

(used to be called combinators in v1)

Facts are features of types, rather than objects. Facts are values added by mixins (such as static variables in a mixin class)

**Name of the company or project** * C++ * https://isocpp.org/ * https://isocpp.org/home/terms-of-use * C * No official logo that I know of, but this color scheme seems to be most...