Tags: szaghi/VecFor
Tags
Refactor library fixing entities renaming Completely refactor the library: the previous entities renaming to obtain multiprecision was non standard thus a deep refactoring has been necessary. Why: Being standard compliant This change addresses the need by: Remove `use, only` aliases relaying much more on preprocessing macros. Side effects: Public API should be backward compatible, but internally many changes happen, it is not clear of possible side effects on third party libraries that consume VecFor for now.
Stable release. add support concurrent multi-kind vector Add support for (concurrent) multi-kind vectors: now vectors can be defined with real32, real64 and real128 kind concurrently, vector_R4P, vector_R8P and vector_R16P respectively. There is still the default vector with the default kind (R8P if no otherwise defined).
PreviousNext