This is a collection of useful (template) classes and functions developed upon standard C++ library. It can be compiled using C++11, but C++17 is more preferable. This README file briefly describes contents of this library and can be not up-do-date, it also gives guidelines on how to use this stuff. For more detailed information see wiki pages.

The collection includes the following functionality:

• implementation of base utility templates such as std::enable_if_t<>, std::index_sequence<>, and other missing stuff for С++11
• iterator helper classes and functions; uxs::zip_iterator<> zip iterator implementation
• standard algorithm and functional extensions
• C++20-like uxs::span<> template type
• standard std::basic_string_view<> implementation for C++11
• some useful utility functions for string manipulation, such as splitting, joining, and searching
• functions for converting UTF-8, UTF-16, UTF-32 to each other
• library for string parsing, formatting and printing
• library for buffered input/output (alternative to rather slow and consuming standard streams), which is compliant with the printing functions
• Z-inflation and Z-deflation support for buffered input/output (zlib integration)
• special buffered input/output derived classes to read and write files inside zip archives (libzip integration)
• dynamic variant object implementation uxs::variant, which can hold data of various types known at runtime and convert one to another (not a template with predefined set of types); it easily integrates with mentioned string parsers and formatters for to and from string conversion
• data structures db::value to store hierarchical records and arrays (json DOM)
• fast full-featured JSON file reader (SAX-like & DOM) and writer
• limited (no DTD and XSL support) XML SAX parser; json-DOM reader and writer for XML
• pretty command line interface (CLI) implementation
• CRC32 calculator
• COW pointer uxs::cow_ptr<> implementation
• insert, erase and find algorithm implementations for bidirectional lists and red-black trees (in the form of functions to make it possible to implement either universal containers or intrusive data structures)
• intrusive bidirectional list implementation
• implementation of uxs::vector<>, uxs::list<>, uxs::set<>, uxs::multiset<>, uxs::map<>, and uxs::multimap<>С++17 specification compliant containers (but which can be compiled using С++11), build upon functions mentioned above (not so useful stuff, but it has academic value)
• standard-compliant pool allocator

This library is not a standalone library, so it doesn't have its own building script or CMakeLists.txt file. Instead, the common way to add this collection to the target project is to use it as git submodule, say, in uxs/ folder. Then, e.g. these lines should be added to the project's CMakeLists.txt:

if(WIN32)
  set(uxs_platform_dir    uxs/platform/win)
elseif(UNIX)
  set(uxs_platform_dir    uxs/platform/posix)
endif()
file(GLOB_RECURSE uxs_includes             uxs/include/*.h)
file(GLOB_RECURSE uxs_sources              uxs/src/*.h;uxs/src/*.cpp)
file(GLOB_RECURSE uxs_platform_includes    ${uxs_platform_dir}/include/*.h)
file(GLOB_RECURSE uxs_platform_sources     ${uxs_platform_dir}/src/*.h;${uxs_platform_dir}/src/*.cpp)

...

add_executable(<project-name>
  ...
  ${uxs_includes}
  ${uxs_sources}
  ${uxs_platform_includes}
  ${uxs_platform_sources}
  ...
)

...

target_include_directories(<project-name> PUBLIC ... uxs/include ...)

Also, uxs needs external file config.h, which could be found and included as #include "uxs/config.h". The simplest way is to add this file in created uxs subfolder of include folder of the project. Here is the minimal contents of this file:

#pragma once
#define UXS_EXPORT

If the project is a library compiled for Windows, and it is needed to export symbols from uxs as well, the recommended contents is the following:

#pragma once
#ifdef <library_name>_EXPORTS
#    define UXS_EXPORT __declspec(dllexport)
#else
#    define UXS_EXPORT __declspec(dllimport)
#endif

This project can be referenced as uxs usage example. It is a separate project for uxs testing and contains lots of use- and test-cases. A simple own test-suite is implemented to sort and organize tests; it involves verification tests with predefined input data, bruteforce-like tests with large amount of random-generated data, and performance tests. Tests from GCC test-suite are also ported for containers testing.