The doc is great! Hoewever some areas are still missing.
C++11 intoduced raw string literals: https://en.cppreference.com/w/cpp/language/string_literal

It is useful in many different areas, like strings with quotes, multiline strings and for example windows paths without escaping backslashes:

const char win_path[] = R"(c:\some\unescaped\path)";

The same cppreference link als

Names map and input are exchanged mistakenly. By sense of Preconditions paragraph they have to be exchanged I suppose, because there is no problem when map and result coincide (in current context).

Segmented reduce uses the same template type OffsetIteratorT for begin and end offsets

static CUB_RUNTIME_FUNCTION cudaError_t cub::DeviceSegmentedReduce::Sum
    (   void *              d_temp_storage,
        size_t &            temp_storage_bytes,
        InputIteratorT      d_in,
        OutputIteratorT     d_out,
        int                 num_segments,
        OffsetIterato

I've recently come to realize that the 'one-size-fits-all' mega-snippets on marzer.github.io/tomlplusplus aren't necessarily useful for everyone, and I should break them up into smaller sub-examples. I'd be totally happy to accept help with this, though that may be wishful thinking!

A new chapter "Interoperability With Other Libraries" should be added to "Use Cases" that will explain QuantityLike concept, quantity_like_traits and explicit construction for a quantity class template. Also, similar documentation should be added (probably more brief) for a quantity_point when #200 is done.

The problem is that the OpenCL types in https://github.com/triSYCL/triSYCL/blob/master/include/triSYCL/opencl_types.hpp are defined on the host according to the x86-64 Linux ABI which depends on the CPU & OS instead of using the description from https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_C.html#built-in-scalar-data-types

Note that the system-wide cl_size_t has been removed

Platform

• SeqAn version: master from around December
• Operating system: RHEL 7
• Compiler: gcc10.2

Description

How to repeat the problem

parser.add_positional_option(p1, "FOO", seqan3::input_file_validator{{"foo.bar"}});

This code is accepted and nothing in the documentation suggests that this doesn't work. But when I pass a file called X.foo.bar