pax_global_header00006660000000000000000000000064142544346170014524gustar00rootroot0000000000000052 comment=a81477931a8aa2ad025c6bda0609f38e09e4d7ec range-v3-0.12.0/000077500000000000000000000000001425443461700132265ustar00rootroot00000000000000range-v3-0.12.0/.buckconfig000066400000000000000000000000001425443461700153270ustar00rootroot00000000000000range-v3-0.12.0/.clang-format000066400000000000000000000057421425443461700156110ustar00rootroot00000000000000{ AccessModifierOffset: -4, AlignAfterOpenBracket: Align, AlignEscapedNewlinesLeft: true, AlignTrailingComments: true, AllowAllParametersOfDeclarationOnNextLine: false, AllowShortBlocksOnASingleLine: true, AllowShortCaseLabelsOnASingleLine: false, AllowShortFunctionsOnASingleLine: None, AllowShortIfStatementsOnASingleLine: false, AllowShortLoopsOnASingleLine: false, AlwaysBreakBeforeMultilineStrings: true, AlwaysBreakAfterReturnType: None, AlwaysBreakTemplateDeclarations: true, BinPackArguments: false, BinPackParameters: true, BraceWrapping: { AfterCaseLabel: true, AfterClass: true, AfterControlStatement: true, AfterEnum: true, AfterFunction: true, AfterNamespace: true, AfterStruct: true, AfterUnion: true, AfterExternBlock: true, BeforeCatch: true, BeforeElse: true, IndentBraces: false, SplitEmptyFunction: false, SplitEmptyRecord: false, SplitEmptyNamespace: true, }, BreakBeforeBinaryOperators: false, BreakBeforeBraces: Custom, BreakBeforeTernaryOperators: true, BreakConstructorInitializers: BeforeComma, BreakInheritanceList: BeforeComma, ColumnLimit: 90, ConstructorInitializerAllOnOneLineOrOnePerLine: false, ConstructorInitializerIndentWidth: 2, ContinuationIndentWidth: 4, Cpp11BracedListStyle: true, DerivePointerAlignment: false, ExperimentalAutoDetectBinPacking: false, ForEachMacros: ['RANGES_FOR',], IncludeBlocks: Regroup, IncludeCategories: [ { Regex: '^$', Priority: 3}, { Regex: '^$', Priority: 2}, { Regex: '^<.*>$', Priority: 1}, ], IndentCaseLabels: false, IndentFunctionDeclarationAfterType: false, IndentWidth: 4, KeepEmptyLinesAtTheStartOfBlocks: true, Language: Cpp, MaxEmptyLinesToKeep: 1, MacroBlockBegin: "^(RANGES|META)_BEGIN_NAMESPACE_(STD|VERSION|CONTAINER)|RANGES_FUNC_BEGIN$", MacroBlockEnd: "^(RANGES|META)_END_NAMESPACE_(STD|VERSION|CONTAINER)|RANGES_FUNC_END$", NamespaceIndentation: All, PenaltyBreakBeforeFirstCallParameter: 10, PenaltyReturnTypeOnItsOwnLine: 1000, PointerAlignment: Middle, SpaceAfterControlStatementKeyword: false, SpaceAfterTemplateKeyword: false, SpaceBeforeAssignmentOperators: true, SpaceBeforeParens: Never, SpaceInEmptyParentheses: false, SpacesBeforeTrailingComments: 1, SpacesInAngles: false, SpacesInCStyleCastParentheses: false, SpacesInParentheses: false, Standard: Cpp11, StatementMacros: [ 'RANGES_INLINE_VARIABLE', 'RANGES_DEFINE_CPO', 'CPP_member', 'CPP_broken_friend_member', ], TabWidth: 4, UseTab: Never, } range-v3-0.12.0/.gitattributes000066400000000000000000000002741425443461700161240ustar00rootroot00000000000000*.hpp text *.cpp text *.txt text *.html text *.md text *.yml text *.xml text *.in text .gitattributes text .gitignore text *.cmd -text *.sln -text *.vcxproj -text *.vcxproj.filters -text range-v3-0.12.0/.github/000077500000000000000000000000001425443461700145665ustar00rootroot00000000000000range-v3-0.12.0/.github/workflows/000077500000000000000000000000001425443461700166235ustar00rootroot00000000000000range-v3-0.12.0/.github/workflows/range-v3-ci.yml000066400000000000000000000434501425443461700213670ustar00rootroot00000000000000name: range-v3 CI # Trigger on pushes to all branches and for all pull-requests on: [push, pull_request] env: CMAKE_VERSION: 3.16.2 NINJA_VERSION: 1.9.0 jobs: build: name: ${{ matrix.config.name }} runs-on: ${{ matrix.config.os }} strategy: fail-fast: false matrix: config: # GCC-6 - { name: "Linux GCC 6 Debug (C++14)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "gcc-6", cxx: "g++-6", cxx_standard: 14, cxx_concepts: false } - { name: "Linux GCC 6 Release (C++14)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-6", cxx: "g++-6", cxx_standard: 14, cxx_concepts: false } - { name: "Linux GCC 6 Debug (C++17)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "gcc-6", cxx: "g++-6", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 6 Release (C++17)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-6", cxx: "g++-6", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 6 Release (C++17, Concepts)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-6", cxx: "g++-6", cxx_standard: 17, } # GCC-7 - { name: "Linux GCC 7 Debug (C++14)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "gcc-7", cxx: "g++-7", cxx_standard: 14, cxx_concepts: false } - { name: "Linux GCC 7 Release (C++14)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-7", cxx: "g++-7", cxx_standard: 14, cxx_concepts: false } - { name: "Linux GCC 7 Debug (C++17)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "gcc-7", cxx: "g++-7", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 7 Release (C++17)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-7", cxx: "g++-7", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 7 Release (C++17, Concepts)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-7", cxx: "g++-7", cxx_standard: 17, } # GCC-8 - { name: "Linux GCC 8 Debug (C++14)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "gcc-8", cxx: "g++-8", cxx_standard: 14, cxx_concepts: false } - { name: "Linux GCC 8 Release (C++14)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-8", cxx: "g++-8", cxx_standard: 14, cxx_concepts: false } - { name: "Linux GCC 8 Debug (C++17)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "gcc-8", cxx: "g++-8", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 8 Release (C++17)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-8", cxx: "g++-8", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 8 Release (C++17, Concepts)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: RelWithDebInfo, cc: "gcc-8", cxx: "g++-8", cxx_standard: 17, } # GCC-9 - { name: "Linux GCC 9 Debug (C++17)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "gcc-9", cxx: "g++-9", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 9 Release (C++17)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: RelWithDebInfo, cc: "gcc-9", cxx: "g++-9", cxx_standard: 17, cxx_concepts: false } - { name: "Linux GCC 9 Debug (C++20)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "gcc-9", cxx: "g++-9", cxx_standard: 20, cxx_concepts: false } - { name: "Linux GCC 9 Release (C++20)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: RelWithDebInfo, cc: "gcc-9", cxx: "g++-9", cxx_standard: 20, cxx_concepts: false } - { name: "Linux GCC 9 Release (C++20, Concepts)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: RelWithDebInfo, cc: "gcc-9", cxx: "g++-9", cxx_standard: 20, } # GCC-10 - { name: "Linux GCC 10 Debug (C++20, Concepts)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "gcc-10", cxx: "g++-10", cxx_standard: 20 } - { name: "Linux GCC 10 Release (C++20, Concepts)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: RelWithDebInfo, cc: "gcc-10", cxx: "g++-10", cxx_standard: 20 } # Clang-5.0 - { name: "Linux Clang 5.0 Debug (C++14 / libc++ / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "clang-5.0", cxx: "clang++-5.0", cxx_standard: 14, cxx_asan: true, libcxx: true } - { name: "Linux Clang 5.0 Debug (C++17 / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "clang-5.0", cxx: "clang++-5.0", cxx_standard: 17, cxx_asan: true, } # Clang-6.0 - { name: "Linux Clang 6.0 Debug (C++14 / libc++ / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "clang-6.0", cxx: "clang++-6.0", cxx_standard: 14, cxx_asan: true, libcxx: true } - { name: "Linux Clang 6.0 Debug (C++17 / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-18.04, build_type: Debug, cc: "clang-6.0", cxx: "clang++-6.0", cxx_standard: 17, cxx_asan: true, } # Clang-8 - { name: "Linux Clang 8 Debug (C++14 / libc++ / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "clang-8", cxx: "clang++-8", cxx_standard: 14, cxx_asan: true, libcxx: true } - { name: "Linux Clang 8 Debug (C++17 / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "clang-8", cxx: "clang++-8", cxx_standard: 17, cxx_asan: true, } # Clang-9 - { name: "Linux Clang 9 Debug (C++17 / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "clang-9", cxx: "clang++-9", cxx_standard: 17, cxx_asan: true, } - { name: "Linux Clang 9 Release (C++17)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: RelWithDebInfo, cc: "clang-9", cxx: "clang++-9", cxx_standard: 17, } # Clang-10 - { name: "Linux Clang 10 Debug (C++20 / ASAN)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: Debug, cc: "clang-10", cxx: "clang++-10", cxx_standard: 20, cxx_asan: true, cxx_concepts: false } - { name: "Linux Clang 10 Release (C++20 / Concepts)", artifact: "Linux.tar.xz", os: ubuntu-latest, build_type: RelWithDebInfo, cc: "clang-10", cxx: "clang++-10", cxx_standard: 20, } # AppleClang - { name: "macOS Clang Debug (C++17)", artifact: "macOS.tar.xz", os: macos-latest, build_type: Debug, cc: "clang", cxx: "clang++", cxx_standard: 17, cxx_asan: true, } - { name: "macOS Clang Release (C++17)", artifact: "macOS.tar.xz", os: macos-latest, build_type: RelWithDebInfo, cc: "clang", cxx: "clang++", cxx_standard: 17, } - { name: "macOS Clang Debug (C++20 / ASAN)", artifact: "macOS.tar.xz", os: macos-latest, build_type: Debug, cc: "clang", cxx: "clang++", cxx_standard: 20, cxx_asan: true, } - { name: "macOS Clang Release (C++20)", artifact: "macOS.tar.xz", os: macos-latest, build_type: RelWithDebInfo, cc: "clang", cxx: "clang++", cxx_standard: 20, } # MSVC 2022 - { name: "Windows MSVC 2022 Debug (C++17)", artifact: "Windows-MSVC.tar.xz", os: windows-latest, build_type: Debug, cc: "cl", cxx: "cl", environment_script: "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Auxiliary/Build/vcvars64.bat", cxx_standard: 17, } - { name: "Windows MSVC 2022 Release (C++17)", artifact: "Windows-MSVC.tar.xz", os: windows-latest, build_type: RelWithDebInfo, cc: "cl", cxx: "cl", environment_script: "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Auxiliary/Build/vcvars64.bat", cxx_standard: 17, } - { name: "Windows MSVC 2022 Debug (C++20)", artifact: "Windows-MSVC.tar.xz", os: windows-latest, build_type: Debug, cc: "cl", cxx: "cl", environment_script: "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Auxiliary/Build/vcvars64.bat", cxx_standard: 20, } - { name: "Windows MSVC 2022 Release (C++20)", artifact: "Windows-MSVC.tar.xz", os: windows-latest, build_type: RelWithDebInfo, cc: "cl", cxx: "cl", environment_script: "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Auxiliary/Build/vcvars64.bat", cxx_standard: 20, } steps: - uses: actions/checkout@v1 - name: Download Ninja and CMake id: cmake_and_ninja shell: cmake -P {0} run: | set(cmake_version $ENV{CMAKE_VERSION}) set(ninja_version $ENV{NINJA_VERSION}) message(STATUS "Using host CMake version: ${CMAKE_VERSION}") if ("${{ runner.os }}" STREQUAL "Windows") set(ninja_suffix "win.zip") set(cmake_suffix "win64-x64.zip") set(cmake_dir "cmake-${cmake_version}-win64-x64/bin") elseif ("${{ runner.os }}" STREQUAL "Linux") set(ninja_suffix "linux.zip") set(cmake_suffix "Linux-x86_64.tar.gz") set(cmake_dir "cmake-${cmake_version}-Linux-x86_64/bin") elseif ("${{ runner.os }}" STREQUAL "macOS") set(ninja_suffix "mac.zip") set(cmake_suffix "Darwin-x86_64.tar.gz") set(cmake_dir "cmake-${cmake_version}-Darwin-x86_64/CMake.app/Contents/bin") endif() set(ninja_url "https://github.com/ninja-build/ninja/releases/download/v${ninja_version}/ninja-${ninja_suffix}") file(DOWNLOAD "${ninja_url}" ./ninja.zip SHOW_PROGRESS) execute_process(COMMAND ${CMAKE_COMMAND} -E tar xvf ./ninja.zip) set(cmake_url "https://github.com/Kitware/CMake/releases/download/v${cmake_version}/cmake-${cmake_version}-${cmake_suffix}") file(DOWNLOAD "${cmake_url}" ./cmake.zip SHOW_PROGRESS) execute_process(COMMAND ${CMAKE_COMMAND} -E tar xvf ./cmake.zip) # Save the path for other steps file(TO_CMAKE_PATH "$ENV{GITHUB_WORKSPACE}/${cmake_dir}" cmake_dir) message("::set-output name=cmake_dir::${cmake_dir}") if (NOT "${{ runner.os }}" STREQUAL "Windows") execute_process( COMMAND chmod +x ninja COMMAND chmod +x ${cmake_dir}/cmake ) endif() - name: Install GCC or Clang id: install_gcc_clang if: startsWith(matrix.config.os, 'ubuntu') shell: bash working-directory: ${{ env.HOME }} run: | sudo apt-get install -y ${{matrix.config.cc}} ${{matrix.config.cxx}} - name: Install libc++ id: install_libcxx if: matrix.config.libcxx shell: bash working-directory: ${{ env.HOME }} env: CC: ${{ matrix.config.cc }} CXX: ${{ matrix.config.cxx }} run: | $GITHUB_WORKSPACE/install_libcxx.sh - name: Configure shell: cmake -P {0} run: | set(ENV{CC} ${{ matrix.config.cc }}) set(ENV{CXX} ${{ matrix.config.cxx }}) if ("${{ runner.os }}" STREQUAL "Windows" AND NOT "x${{ matrix.config.environment_script }}" STREQUAL "x") execute_process( COMMAND "${{ matrix.config.environment_script }}" && set OUTPUT_FILE environment_script_output.txt ) set(cxx_flags "/permissive- /EHsc") file(STRINGS environment_script_output.txt output_lines) foreach(line IN LISTS output_lines) if (line MATCHES "^([a-zA-Z0-9_-]+)=(.*)$") set(ENV{${CMAKE_MATCH_1}} "${CMAKE_MATCH_2}") endif() endforeach() endif() set(path_separator ":") if ("${{ runner.os }}" STREQUAL "Windows") set(path_separator ";") endif() set(ENV{PATH} "$ENV{GITHUB_WORKSPACE}${path_separator}$ENV{PATH}") if ("x${{ matrix.config.libcxx }}" STREQUAL "xtrue") set(cxx_flags "${cxx_flags} -stdlib=libc++ -nostdinc++ -cxx-isystem $ENV{GITHUB_WORKSPACE}/llvm/include/c++/v1/ -Wno-unused-command-line-argument") set(link_flags "${link_flags} -L $ENV{GITHUB_WORKSPACE}/llvm/lib -Wl,-rpath,$ENV{GITHUB_WORKSPACE}/llvm/lib -lc++abi") endif() if ("${{ matrix.config.cxx }}" MATCHES "clang.*") # clang spurious warning on <=> use set(cxx_flags "${cxx_flags} -Wno-zero-as-null-pointer-constant") endif() if ("x${{ matrix.config.cxx_asan }}" STREQUAL "xtrue") set(cxx_flags "${cxx_flags} -fsanitize=address -fno-omit-frame-pointer") endif() set(cxx_concepts ON) if ("x${{ matrix.config.cxx_concepts }}" STREQUAL "xfalse") set(cxx_concepts OFF) endif() execute_process( COMMAND ${{ steps.cmake_and_ninja.outputs.cmake_dir }}/cmake -S . -B build -G Ninja -D CMAKE_BUILD_TYPE=${{ matrix.config.build_type }} -D CMAKE_MAKE_PROGRAM:STRING=ninja -D CMAKE_CXX_STANDARD:STRING=${{ matrix.config.cxx_standard }} -D "CMAKE_CXX_FLAGS:STRING=${cxx_flags}" -D "CMAKE_EXE_LINKER_FLAGS:STRING=${link_flags}" -D CMAKE_VERBOSE_MAKEFILE:BOOL=ON -D RANGE_V3_HEADER_CHECKS:BOOL=ON -D RANGES_PREFER_REAL_CONCEPTS:BOOL=${cxx_concepts} ${{ matrix.config.cmake_args }} ${extra_cmake_args} RESULT_VARIABLE result ) if (NOT result EQUAL 0) message(FATAL_ERROR "Bad exit status") endif() - name: Build shell: cmake -P {0} continue-on-error: ${{ matrix.config.experimental || false }} run: | set(ENV{NINJA_STATUS} "[%f/%t %o/sec] ") if ("${{ runner.os }}" STREQUAL "Windows" AND NOT "x${{ matrix.config.environment_script }}" STREQUAL "x") file(STRINGS environment_script_output.txt output_lines) foreach(line IN LISTS output_lines) if (line MATCHES "^([a-zA-Z0-9_-]+)=(.*)$") set(ENV{${CMAKE_MATCH_1}} "${CMAKE_MATCH_2}") endif() endforeach() endif() set(path_separator ":") if ("${{ runner.os }}" STREQUAL "Windows") set(path_separator ";") endif() set(ENV{PATH} "$ENV{GITHUB_WORKSPACE}${path_separator}$ENV{PATH}") execute_process( COMMAND ${{ steps.cmake_and_ninja.outputs.cmake_dir }}/cmake --build build RESULT_VARIABLE result ) if (NOT result EQUAL 0) message(FATAL_ERROR "Bad exit status") endif() - name: Run tests shell: cmake -P {0} continue-on-error: ${{ matrix.config.experimental || false }} run: | include(ProcessorCount) ProcessorCount(N) set(ENV{CTEST_OUTPUT_ON_FAILURE} "ON") execute_process( COMMAND ${{ steps.cmake_and_ninja.outputs.cmake_dir }}/ctest --verbose -j ${N} WORKING_DIRECTORY build RESULT_VARIABLE result ) if (NOT result EQUAL 0) message(FATAL_ERROR "Running tests failed!") endif() range-v3-0.12.0/.gitignore000066400000000000000000000077651425443461700152350ustar00rootroot00000000000000## Copyright (c) 2013 GitHub, Inc. ## ## Permission is hereby granted, free of charge, to any person obtaining a ## copy of this software and associated documentation files (the "Software"), ## to deal in the Software without restriction, including without limitation ## the rights to use, copy, modify, merge, publish, distribute, sublicense, ## and/or sell copies of the Software, and to permit persons to whom the ## Software is furnished to do so, subject to the following conditions: ## ## The above copyright notice and this permission notice shall be included in ## all copies or substantial portions of the Software. ## ## THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR ## IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, ## FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE ## AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER ## LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING ## FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER ## DEALINGS IN THE SOFTWARE. # Compiled Object files *.slo *.lo *.o *.obj # Compiled Dynamic libraries *.so *.dylib *.dll # Compiled Static libraries *.lai *.la *.a *.lib # Executables *.exe *.out *.app # Clion files .idea ## Ignore Visual Studio temporary files, build results, and ## files generated by popular Visual Studio add-ons. # User-specific files *.suo *.user *.sln.docstates # Build results [Dd]ebug/ [Dd]ebugPublic/ [Rr]elease/ x64/ build*/ bld/ [Bb]in/ [Oo]bj/ bazel-* cmake-build-*/ # Enable "build/" folder in the NuGet Packages folder since NuGet packages use it for MSBuild targets !packages/*/build/ # MSTest test Results [Tt]est[Rr]esult*/ [Bb]uild[Ll]og.* #NUNIT *.VisualState.xml TestResult.xml *_i.c *_p.c *_i.h *.ilk *.meta *.obj *.pch *.pdb *.pgc *.pgd *.rsp *.sbr *.tlb *.tli *.tlh *.tmp *.tmp_proj *.log *.vspscc *.vssscc .builds *.pidb *.svclog *.scc # Visual C++ cache files ipch/ *.aps *.ncb *.opensdf *.sdf *.cachefile # Visual Studio profiler *.psess *.vsp *.vspx # TFS 2012 Local Workspace $tf/ # Guidance Automation Toolkit *.gpState # ReSharper is a .NET coding add-in _ReSharper*/ *.[Rr]e[Ss]harper *.DotSettings.user # JustCode is a .NET coding addin-in .JustCode # TeamCity is a build add-in _TeamCity* # DotCover is a Code Coverage Tool *.dotCover # NCrunch *.ncrunch* _NCrunch_* .*crunch*.local.xml # MightyMoose *.mm.* AutoTest.Net/ # Installshield output folder [Ee]xpress/ # DocProject is a documentation generator add-in DocProject/buildhelp/ DocProject/Help/*.HxT DocProject/Help/*.HxC DocProject/Help/*.hhc DocProject/Help/*.hhk DocProject/Help/*.hhp DocProject/Help/Html2 DocProject/Help/html # Click-Once directory publish/ # Publish Web Output *.Publish.xml *.azurePubxml # NuGet Packages Directory ## TODO: If you have NuGet Package Restore enabled, uncomment the next line #packages/ ## TODO: If the tool you use requires repositories.config, also uncomment the next line #!packages/repositories.config # Windows Azure Build Output csx/ *.build.csdef # Windows Store app package directory AppPackages/ # Buck build artefacts .buckd/ buck-out/ # Others sql/ *.Cache ClientBin/ [Ss]tyle[Cc]op.* ~$* *~ *.dbmdl *.dbproj.schemaview *.[Pp]ublish.xml *.pfx *.publishsettings .DS_Store # RIA/Silverlight projects Generated_Code/ # Backup & report files from converting an old project file to a newer # Visual Studio version. Backup files are not needed, because we have git ;-) _UpgradeReport_Files/ Backup*/ UpgradeLog*.XML UpgradeLog*.htm # SQL Server files App_Data/*.mdf App_Data/*.ldf # Business Intelligence projects *.rdl.data *.bim.layout *.bim_*.settings # Microsoft Fakes FakesAssemblies/ # ========================= # Windows detritus # ========================= # Windows image file caches Thumbs.db ehthumbs.db # Folder config file Desktop.ini # Recycle Bin used on file shares $RECYCLE.BIN/ # Visual Studio stuff *.VC.db *.VC.opendb .vscode/ .vs/ .history/ .devcontainer/ \#*# .#* /CMakeSettings.json range-v3-0.12.0/.gitmodules000066400000000000000000000001661425443461700154060ustar00rootroot00000000000000[submodule "doc/gh-pages"] path = doc/gh-pages url = https://github.com/ericniebler/range-v3.git branch = gh-pages range-v3-0.12.0/.vscode/000077500000000000000000000000001425443461700145675ustar00rootroot00000000000000range-v3-0.12.0/.vscode/c_cpp_properties.json000066400000000000000000000051111425443461700210200ustar00rootroot00000000000000{ "configurations": [ { "name": "Mac", "includePath": [ "/Users/eniebler/llvm-install/include/c++/v1", "/usr/local/include", "/Users/eniebler/llvm-install/lib/clang/6.0.0/include", "/usr/include", "${workspaceRoot}/include", "/usr/local/opt/boost@1.67/incluse" ], "defines": [], "intelliSenseMode": "clang-x64", "browse": { "path": [ "/Users/eniebler/llvm-install/include/c++/v1", "/usr/local/include", "/Users/eniebler/llvm-install/lib/clang/6.0.0/include", "/usr/include", "${workspaceRoot}/include", "/usr/local/opt/boost@1.67/incluse" ], "limitSymbolsToIncludedHeaders": true, "databaseFilename": "" }, "macFrameworkPath": [ "/System/Library/Frameworks", "/Library/Frameworks" ], "compilerPath": "/Users/eniebler/llvm-install/bin/clang++", "cStandard": "c11", "cppStandard": "c++11", "configurationProvider": "vector-of-bool.cmake-tools" }, { "name": "Linux", "includePath": [ "/usr/include", "/usr/local/include", "${workspaceRoot}/include" ], "defines": [], "intelliSenseMode": "clang-x64", "browse": { "path": [ "/usr/include", "/usr/local/include", "${workspaceRoot}/include" ], "limitSymbolsToIncludedHeaders": true, "databaseFilename": "" }, "cStandard": "c11", "cppStandard": "c++11", "configurationProvider": "ms-vscode.cmake-tools" }, { "name": "Win32", "includePath": [ "${workspaceRoot}/include" ], "defines": [ "_DEBUG", "UNICODE" ], "intelliSenseMode": "msvc-x64", "browse": { "path": [ "${workspaceRoot}/include" ], "limitSymbolsToIncludedHeaders": true, "databaseFilename": "" }, "cStandard": "c11", "cppStandard": "c++11" } ], "version": 4 }range-v3-0.12.0/.vscode/settings.json000066400000000000000000000055431425443461700173310ustar00rootroot00000000000000{ "files.associations": { "iterator": "cpp", "*.ipp": "cpp", "array": "cpp", "deque": "cpp", "forward_list": "cpp", "list": "cpp", "unordered_map": "cpp", "unordered_set": "cpp", "vector": "cpp", "initializer_list": "cpp", "string_view": "cpp", "*.tcc": "cpp", "atomic": "cpp", "bit": "cpp", "bitset": "cpp", "cctype": "cpp", "chrono": "cpp", "clocale": "cpp", "cmath": "cpp", "condition_variable": "cpp", "cstdarg": "cpp", "cstddef": "cpp", "cstdint": "cpp", "cstdio": "cpp", "cstdlib": "cpp", "cstring": "cpp", "ctime": "cpp", "cwchar": "cpp", "cwctype": "cpp", "map": "cpp", "set": "cpp", "exception": "cpp", "fstream": "cpp", "functional": "cpp", "iosfwd": "cpp", "iostream": "cpp", "istream": "cpp", "limits": "cpp", "memory": "cpp", "memory_resource": "cpp", "mutex": "cpp", "new": "cpp", "numeric": "cpp", "optional": "cpp", "ostream": "cpp", "ratio": "cpp", "regex": "cpp", "shared_mutex": "cpp", "sstream": "cpp", "stdexcept": "cpp", "streambuf": "cpp", "string": "cpp", "system_error": "cpp", "thread": "cpp", "type_traits": "cpp", "tuple": "cpp", "typeinfo": "cpp", "utility": "cpp", "__config": "cpp", "__bit_reference": "cpp", "__debug": "cpp", "__functional_base": "cpp", "__locale": "cpp", "__mutex_base": "cpp", "__nullptr": "cpp", "__threading_support": "cpp", "__tuple": "cpp", "coroutine": "cpp", "ios": "cpp", "locale": "cpp", "random": "cpp", "__node_handle": "cpp", "__tree": "cpp", "climits": "cpp", "__memory": "cpp", "strstream": "cpp", "complex": "cpp", "iomanip": "cpp", "cinttypes": "cpp", "typeindex": "cpp", "variant": "cpp", "__split_buffer": "cpp", "filesystem": "cpp", "queue": "cpp", "stack": "cpp", "__errc": "cpp", "__hash_table": "cpp", "__string": "cpp", "algorithm": "cpp", "codecvt": "cpp", "valarray": "cpp", "version": "cpp", "source_location": "cpp", "span": "cpp", "ranges": "cpp", "compare": "cpp", "concepts": "cpp", "stop_token": "cpp", "cfenv": "cpp", "__bits": "cpp", "numbers": "cpp", "semaphore": "cpp" }, "C_Cpp.configurationWarnings": "Disabled", "cmake.configureOnOpen": true, "C_Cpp.intelliSenseEngineFallback": "Enabled" } range-v3-0.12.0/.vscode/tasks.json000066400000000000000000000015541425443461700166140ustar00rootroot00000000000000{ // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format "version": "2.0.0", "options": { "cwd": "${workspaceRoot}/../range-build" }, "tasks": [ { "label": "cmake", "type": "shell", "command": "cmake -G 'Unix Makefiles' -DCMAKE_BUILD_TYPE=Debug ../range-v3", "group": "build", "presentation": { "reveal": "always", "panel": "new" } }, { "label": "make", "type": "shell", "command": "make -j8", "group": { "kind": "build", "isDefault": true }, "presentation": { "reveal": "always", "panel": "new" } } ] } range-v3-0.12.0/BUCK000066400000000000000000000013251425443461700136760ustar00rootroot00000000000000prebuilt_cxx_library( name = 'concepts', header_namespace = 'concepts', header_only = True, exported_headers = subdir_glob([ ('include/concepts', '**/*.hpp'), ]), licenses = [ 'LICENSE.txt', ], ) prebuilt_cxx_library( name = 'meta', header_namespace = 'meta', header_only = True, exported_headers = subdir_glob([ ('include/meta', '**/*.hpp'), ]), licenses = [ 'LICENSE.txt', ], ) prebuilt_cxx_library( name = 'range-v3', header_namespace = 'range/v3', header_only = True, exported_headers = subdir_glob([ ('include/range/v3', '**/*.hpp'), ]), licenses = [ 'LICENSE.txt', ], visibility = [ 'PUBLIC' ], deps = [ ':concepts', ':meta', ], ) range-v3-0.12.0/BUILD.bazel000066400000000000000000000010441425443461700151030ustar00rootroot00000000000000cc_library( name = 'concepts', hdrs = glob([ 'include/concepts/**/*.hpp', ]), includes = [ "include", ], ) cc_library( name = 'meta', hdrs = glob([ 'include/meta/**/*.hpp', ]), includes = [ "include", ], ) cc_library( name = 'std', hdrs = glob([ 'include/std/**/*.hpp', ]), includes = [ "include", ], ) cc_library( name = 'range-v3', hdrs = glob([ 'include/range/v3/**/*.hpp', ]), visibility = ["//visibility:public"], deps = [ ':concepts', ':meta', ':std', ], ) range-v3-0.12.0/CMakeLists.txt000066400000000000000000000177221425443461700157770ustar00rootroot00000000000000# Copyright Eric Niebler 2014 # Copyright Gonzalo Brito Gadeschi 2014, 2017 # Copyright Louis Dionne 2015 # Copyright Casey Carter 2016 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) cmake_minimum_required(VERSION 3.6) get_directory_property(is_subproject PARENT_DIRECTORY) if(NOT is_subproject) set(is_standalone YES) else() set(is_standalone NO) endif() project(Range-v3 CXX) list(APPEND CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/cmake") set(CMAKE_EXPORT_COMPILE_COMMANDS ON) # Export compilation data-base set_property(GLOBAL PROPERTY USE_FOLDERS ON) include(ranges_options) include(ranges_env) include(ranges_flags) add_library(range-v3-meta INTERFACE) add_library(range-v3::meta ALIAS range-v3-meta) target_include_directories(range-v3-meta INTERFACE $) target_include_directories(range-v3-meta SYSTEM INTERFACE $/include>) target_compile_options(range-v3-meta INTERFACE $<$:/permissive-> $<$:-Xcompiler=/permissive->) add_library(range-v3-concepts INTERFACE) add_library(range-v3::concepts ALIAS range-v3-concepts) target_include_directories(range-v3-concepts INTERFACE $) target_include_directories(range-v3-concepts SYSTEM INTERFACE $/include>) target_compile_options(range-v3-concepts INTERFACE $<$:/permissive-> $<$:-Xcompiler=/permissive->) target_link_libraries(range-v3-concepts INTERFACE range-v3::meta) add_library(range-v3 INTERFACE) add_library(range-v3::range-v3 ALIAS range-v3) target_include_directories(range-v3 INTERFACE $) target_include_directories(range-v3 SYSTEM INTERFACE $/include>) target_compile_options(range-v3 INTERFACE $<$:/permissive-> $<$:-Xcompiler=/permissive->) target_link_libraries(range-v3 INTERFACE range-v3::concepts range-v3::meta) function(rv3_add_test TESTNAME EXENAME FIRSTSOURCE) add_executable(range.v3.${EXENAME} ${FIRSTSOURCE} ${ARGN}) target_link_libraries(range.v3.${EXENAME} range-v3) add_test(range.v3.${TESTNAME} range.v3.${EXENAME}) endfunction(rv3_add_test) if(RANGE_V3_DOCS) add_subdirectory(doc) endif() if(RANGE_V3_TESTS) include(CTest) add_subdirectory(test) endif() if(RANGE_V3_EXAMPLES) add_subdirectory(example) endif() if(RANGE_V3_PERF) include(gtest) include(gbenchmark) add_subdirectory(perf) endif() # Add header files as sources to fix MSVS 2017 not finding source during debugging file(GLOB_RECURSE RANGE_V3_PUBLIC_HEADERS_ABSOLUTE "${CMAKE_CURRENT_SOURCE_DIR}/include/*.hpp") add_custom_target(range.v3.headers SOURCES ${RANGE_V3_PUBLIC_HEADERS_ABSOLUTE}) set_target_properties(range.v3.headers PROPERTIES FOLDER "header") # Test all headers if(RANGE_V3_HEADER_CHECKS) include(TestHeaders) file(GLOB_RECURSE RANGE_V3_PUBLIC_HEADERS RELATIVE "${CMAKE_CURRENT_SOURCE_DIR}/include" "${CMAKE_CURRENT_SOURCE_DIR}/include/*.hpp") # These headers are not meant to be included directly: list(REMOVE_ITEM RANGE_V3_PUBLIC_HEADERS std/detail/associated_types.hpp) list(REMOVE_ITEM RANGE_V3_PUBLIC_HEADERS range/v3/detail/epilogue.hpp) # Deprecated headers if(CMAKE_CXX_COMPILER_ID STREQUAL GNU) foreach(header ${RANGE_V3_PUBLIC_HEADERS}) file(STRINGS "${CMAKE_CURRENT_SOURCE_DIR}/include/${header}" is_deprecated LIMIT_COUNT 1 REGEX ".*RANGES_DEPRECATED_HEADER.*") if(is_deprecated) list(APPEND RANGE_V3_DEPRECATED_PUBLIC_HEADERS "${header}") endif() endforeach() endif() if(NOT RANGE_V3_COROUTINE_FLAGS) # Can't test this header if we can't even compile it list(APPEND RANGE_V3_DEPRECATED_PUBLIC_HEADERS range/v3/experimental/utility/generator.hpp) endif() add_header_test(test.range.v3.headers EXCLUDE ${RANGE_V3_DEPRECATED_PUBLIC_HEADERS} HEADERS ${RANGE_V3_PUBLIC_HEADERS}) target_link_libraries(test.range.v3.headers PRIVATE range-v3) endif() # Grab the range-v3 version numbers: include(${CMAKE_CURRENT_SOURCE_DIR}/Version.cmake) set(RANGE_V3_VERSION ${RANGE_V3_MAJOR}.${RANGE_V3_MINOR}.${RANGE_V3_PATCHLEVEL}) # Try to build a new version.hpp configure_file(version.hpp.in include/range/v3/version.hpp @ONLY) file(STRINGS ${CMAKE_CURRENT_BINARY_DIR}/include/range/v3/version.hpp RANGE_V3_OLD_VERSION_HPP) file(STRINGS ${CMAKE_CURRENT_SOURCE_DIR}/include/range/v3/version.hpp RANGE_V3_NEW_VERSION_HPP) # If the new version.hpp is materially different from the one in the source # directory, update it, commit, and tag. if(NOT RANGE_V3_NEW_VERSION_HPP STREQUAL RANGE_V3_OLD_VERSION_HPP) # Check that doc/release_notes.md and Version.cmake are the only changed file: execute_process( COMMAND ${GIT_EXECUTABLE} -C "${CMAKE_CURRENT_SOURCE_DIR}" status --porcelain -uno OUTPUT_VARIABLE RANGE_V3_GIT_STATUS OUTPUT_STRIP_TRAILING_WHITESPACE ) string(REPLACE "\n" ";" RANGE_V3_GIT_STATUS ${RANGE_V3_GIT_STATUS}) if (NOT "x${RANGE_V3_GIT_STATUS}" STREQUAL "x M Version.cmake; M doc/release_notes.md") message(FATAL_ERROR "Cannot update version.hpp: range-v3 source directory has a dirty status") endif() file( COPY ${CMAKE_CURRENT_BINARY_DIR}/include/range/v3/version.hpp DESTINATION ${CMAKE_CURRENT_SOURCE_DIR}/include/range/v3 ) execute_process( COMMAND ${GIT_EXECUTABLE} -C "${CMAKE_CURRENT_SOURCE_DIR}" add -u ) execute_process( COMMAND ${GIT_EXECUTABLE} -C "${CMAKE_CURRENT_SOURCE_DIR}" commit -m "${RANGE_V3_VERSION}" ) execute_process( COMMAND ${GIT_EXECUTABLE} -C "${CMAKE_CURRENT_SOURCE_DIR}" tag -f -a "${RANGE_V3_VERSION}" -m "${RANGE_V3_VERSION}" ) find_program(CONAN_EXECUTABLE NAMES conan conan.exe) if (NOT "x${CONAN_EXECUTABLE}" STREQUAL "xCONAN_EXECUTABLE-NOTFOUND") message(STATUS "Exporting conanfile for new version") execute_process( COMMAND ${CONAN_EXECUTABLE} create . range-v3/${RANGE_V3_VERSION}@ericniebler/stable WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}" ) endif() message(STATUS "Version updated to ${RANGE_V3_VERSION}. Don't forget to:") message(STATUS " git push origin ") message(STATUS "and (after that is merged to master) then:") message(STATUS " conan remote add range-v3 https://api.bintray.com/conan/range-v3/range-v3") message(STATUS " conan create ${CMAKE_CURRENT_SOURCE_DIR} range-v3/${RANGE_V3_VERSION}@ericniebler/stable") message(STATUS " conan upload --all range-v3/${RANGE_V3_VERSION}@ericniebler/stable -r=range-v3") endif() include(CMakePackageConfigHelpers) # write_basic_package_version_file(...) gained ARCH_INDEPENDENT in CMake 3.14. # For CMake 3.6, this workaround makes the version file ARCH_INDEPENDENT # by making CMAKE_SIZEOF_VOID_P empty. set(OLD_CMAKE_SIZEOF_VOID_P ${CMAKE_SIZEOF_VOID_P}) set(CMAKE_SIZEOF_VOID_P "") write_basic_package_version_file( ${CMAKE_CURRENT_BINARY_DIR}/range-v3-config-version.cmake VERSION ${RANGE_V3_VERSION} COMPATIBILITY ExactVersion ) set(CMAKE_SIZEOF_VOID_P ${OLD_CMAKE_SIZEOF_VOID_P}) include(GNUInstallDirs) install(TARGETS range-v3-concepts range-v3-meta range-v3 EXPORT range-v3-targets DESTINATION ${CMAKE_INSTALL_LIBDIR}) install(EXPORT range-v3-targets FILE range-v3-targets.cmake DESTINATION ${CMAKE_INSTALL_LIBDIR}/cmake/range-v3) install(FILES ${CMAKE_CURRENT_BINARY_DIR}/range-v3-config-version.cmake cmake/range-v3-config.cmake DESTINATION ${CMAKE_INSTALL_LIBDIR}/cmake/range-v3) install(DIRECTORY include/ DESTINATION ${CMAKE_INSTALL_INCLUDEDIR} FILES_MATCHING PATTERN "*") export(EXPORT range-v3-targets FILE range-v3-config.cmake) range-v3-0.12.0/CREDITS.md000066400000000000000000000112301425443461700146420ustar00rootroot00000000000000Acknowledgements ---------------- In range-v3, I have integrated many ideas that come from other people. I would be remiss to not mention them. Many others helped either directly or indirectly in a variety of ways. In no particular order... | Contributor | Contribution | |-----------------------------|------| | Jeremy Siek | Container algorithms (in Boost pre-history), Boost.Iterators | | Thorston Ottoson | Boost.Range v1 | | Neil Groves | Boost.Range v2 | | David Abrahams, Thomas Witt | Boost.Iterators, Sentinels | | Sean Parent | ASL, Projections, View / Range distinction, much Generic Program wisdom besides | | Dietmar Kühl | Array Traits, Property Map | | Andrew Sutton | C++ Concepts "Lite", Origin Libraries, Palo Alto Report | | Doug Gregor | C++0x Concepts | | Casey Carter | Co-author and Editor, Ranges TS; major code contributions | | Gonzalo Brito Gadeschi | Many ideas, bug reports, and code contributions | | Alexander Stepanov | STL, Generic Programming, Iterators, Elements of Programming, etc. | | Bjarne Stroustrup | A tireless effort to add proper support for Generic Programming to C++, early support for my Ranges proposal | | Herb Sutter | Early support for my Ranges proposal | | The Standard C++ Foundation | A generous grant supporting my Ranges work | An Abreviated History -------------------- **Range v1** I came to Boost in the early 2000's. By that time, Boost already had a Range library (Thorston Ottoson's). At this time, Boost.Range was little more that the `begin` and `end` free functions, and range-based overloads of the STL algorithms that dispatched to the iterator-based overloads in namespace `std`. Boost also already had the Iterators library by David Abrahams and Jeremy Siek. This library had iterator adaptors like `filter_iterator` and `transform_iterator`. **Range v2** It seemed natural to me that the Range library and the adaptors from the Iterators library should be combined. I wrote the `filter` and `transform` range adaptors, commandeered the pipe operator (`|`) from bash for chaining, and put a rough library together called Range_ex in the Boost File Vault (which would later become the Boost Sandbox). I saw problems with my design and never finished it. A few years later, Neil Groves picked up some of the ideas in my Range\_ex, polished them a great deal, published his own Range\_ex library, and submitted it to Boost. It became Boost.Range v2. At the time of writing (March, 2017), it is the version still shipping with Boost. **Range v3** In 2013, I published a blog post called ["Out Parameters, Move Semantics, and Stateful Algorithms"](http://ericniebler.com/2013/10/13/out-parameters-vs-move-semantics/) that turned my mind to ranges once again. Following that, it became clear to me that the Boost.Range library, designed for C++98, needed a facelift for the post-C++11 world. I began what I believed at the time would be a quick hack to bring Boost.Range into the modern world. I called it "Range v3", thinking it would become the third major version of the Boost.Range library. Subsequent posts detailed the evolution of my thinking as range-v3 took shape. **Standardization** Around this time, some big thinkers in the C++ community were working to resurrect the effort to add Concepts to C++. They published a paper ([N3351](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3351.pdf)) that would become known as the **"Palo Alto Report"** which detailed the necessary and sufficient language and library support for a concept-checked version of the Standard Template Library. The authors of the paper included Alexander Stepanov, Bjarne Stroustrup, Sean Parent, Andrew Sutton, and more. Andrew Sutton began working in earnest to realize the core language changes, an effort that became known as "Concepts Lite". It became the Concepts TS and ultimately C++20's `concept` language feature. I realized early on that Concepts Lite, or something like it, would become part of Standard C++. Recognizing that C++ would need a concept-ified Standard Library to go with the language feature, I began evolving range-v3 in that direction, eventually submitting ["Ranges for the Standard Library, Revision 1"](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4128.html) to the C++ Standardization Committee, together with Andrew Sutton and Sean Parent. The Committee approved the direction in late 2014, and so it goes... As of today (2022-06), C++20 has shipped with modest ranges support in the `std::ranges` namespace, with *much* more to come in C++23 and beyond. Stay tuned. range-v3-0.12.0/LICENSE.txt000066400000000000000000000161011425443461700150500ustar00rootroot00000000000000======================================================== Boost Software License - Version 1.0 - August 17th, 2003 ======================================================== Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following: The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ============================================================================== libc++ License ============================================================================== The libc++ library is dual licensed under both the University of Illinois "BSD-Like" license and the MIT license. As a user of this code you may choose to use it under either license. As a contributor, you agree to allow your code to be used under both. Full text of the relevant licenses is included below. ============================================================================== University of Illinois/NCSA Open Source License Copyright (c) 2009-2014 by the contributors listed in CREDITS.TXT http://llvm.org/svn/llvm-project/libcxx/trunk/CREDITS.TXT All rights reserved. Developed by: LLVM Team University of Illinois at Urbana-Champaign http://llvm.org Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal with the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimers. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimers in the documentation and/or other materials provided with the distribution. * Neither the names of the LLVM Team, University of Illinois at Urbana-Champaign, nor the names of its contributors may be used to endorse or promote products derived from this Software without specific prior written permission. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE SOFTWARE. ============================================================================== Copyright (c) 2009-2014 by the contributors listed in CREDITS.TXT http://llvm.org/svn/llvm-project/libcxx/trunk/CREDITS.TXT Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ============================================================================== Stepanov and McJones, "Elements of Programming" license ============================================================================== // Copyright (c) 2009 Alexander Stepanov and Paul McJones // // Permission to use, copy, modify, distribute and sell this software // and its documentation for any purpose is hereby granted without // fee, provided that the above copyright notice appear in all copies // and that both that copyright notice and this permission notice // appear in supporting documentation. The authors make no // representations about the suitability of this software for any // purpose. It is provided "as is" without express or implied // warranty. // // Algorithms from // Elements of Programming // by Alexander Stepanov and Paul McJones // Addison-Wesley Professional, 2009 ============================================================================== SGI C++ Standard Template Library license ============================================================================== // Copyright (c) 1994 // Hewlett-Packard Company // // Permission to use, copy, modify, distribute and sell this software // and its documentation for any purpose is hereby granted without fee, // provided that the above copyright notice appear in all copies and // that both that copyright notice and this permission notice appear // in supporting documentation. Hewlett-Packard Company makes no // representations about the suitability of this software for any // purpose. It is provided "as is" without express or implied warranty. // // Copyright (c) 1996 // Silicon Graphics Computer Systems, Inc. // // Permission to use, copy, modify, distribute and sell this software // and its documentation for any purpose is hereby granted without fee, // provided that the above copyright notice appear in all copies and // that both that copyright notice and this permission notice appear // in supporting documentation. Silicon Graphics makes no // representations about the suitability of this software for any // purpose. It is provided "as is" without express or implied warranty. // range-v3-0.12.0/README.md000066400000000000000000000214371425443461700145140ustar00rootroot00000000000000range-v3 ======== Range library for C++14/17/20. This code was the basis of [a formal proposal](https://ericniebler.github.io/std/wg21/D4128.html) to add range support to the C++ standard library. That proposal evolved through a Technical Specification, and finally into [P0896R4 "The One Ranges Proposal"](https://wg21.link/p0896r4) which was merged into the C++20 working drafts in November 2018. About: ------ Ranges are an extension of the Standard Template Library that makes its iterators and algorithms more powerful by making them _composable_. Unlike other range-like solutions which seek to do away with iterators, in range-v3 ranges are an abstration layer _on top_ of iterators. Range-v3 is built on three pillars: Views, Actions, and Algorithms. The algorithms are the same as those with which you are already familiar in the STL, except that in range-v3 all the algorithms have overloads that take ranges in addition to the overloads that take iterators. Views are composable adaptations of ranges where the adaptation happens lazily as the view is iterated. And an action is an eager application of an algorithm to a container that mutates the container in-place and returns it for further processing. Views and actions use the pipe syntax (e.g., `rng | adapt1 | adapt2 | ...`) so your code is terse and readable from left to right. Documentation: -------------- Check out the (woefully incomplete) documentation [here](https://ericniebler.github.io/range-v3/). Other resources (mind the dates, the library probably has changed since then): - Usage: - Talk: [CppCon 2015: Eric Niebler "Ranges for the Standard Library"](https://www.youtube.com/watch?v=mFUXNMfaciE), 2015. - [A slice of Python in C++](http://ericniebler.com/2014/12/07/a-slice-of-python-in-c/), 07.12.2014. - Actions (back then called [Container Algorithms](http://ericniebler.com/2014/11/23/container-algorithms/)), 23.11.2014. - [Range comprehensions](http://ericniebler.com/2014/04/27/range-comprehensions/), 27.04.2014. - [Input iterators vs input ranges](http://ericniebler.com/2013/11/07/input-iterators-vs-input-ranges/), 07.11.2013. - Design / Implementation: - Rationale behind range-v3: [N4128: Ranges for the standard library Revision 1](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4128.html), 2014. - Ranges TS: [N4560: C++ Extensions for Ranges](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4560.pdf), 2015. - Implementation of customization points in range-v3: - [N4381: Suggested Design for Customization Points](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4381.html), 2015. - [P0386: Inline variables](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0386r0.pdf), 2016. - [Customization Point Design in C++11 and Beyond](http://ericniebler.com/2014/10/21/customization-point-design-in-c11-and-beyond/), 2014. - Proxy iterators in range-v3: - [D0022: Proxy Iterators for the Ranges Extensions](https://ericniebler.github.io/std/wg21/D0022.html). - [To Be or Not to Be (an Iterator)](http://ericniebler.com/2015/01/28/to-be-or-not-to-be-an-iterator/), 2015. - [Iterators++: Part1](http://ericniebler.com/2015/02/03/iterators-plus-plus-part-1/), 2015. - [Iterators++: Part2](http://ericniebler.com/2015/02/13/iterators-plus-plus-part-2/), 2015. - [Iterators++: Part3](http://ericniebler.com/2015/03/03/iterators-plus-plus-part-3/), 2015. - Metaprogramming utilities: - See the [meta documentation](https://ericniebler.github.io/meta/index.html), the library has changed significantly since the [2014 blog post](http://ericniebler.com/2014/11/13/tiny-metaprogramming-library/). - Concept emulation layer: [Concept checking in C++11](http://ericniebler.com/2013/11/23/concept-checking-in-c11/), 2013. - [C++Now 2014: Eric Niebler "C++11 Library Design"](https://www.youtube.com/watch?v=zgOF4NrQllo), 2014. License: -------- Most of the source code in this project are mine, and those are under the Boost Software License. Parts are taken from Alex Stepanov's Elements of Programming, Howard Hinnant's libc++, and from the SGI STL. Please see the attached LICENSE file and the CREDITS file for the licensing and acknowledgments. Supported Compilers ------------------- The code is known to work on the following compilers: - clang 5.0 (or later) - GCC 6.5 (or later) - Clang/LLVM 6 (or later) on Windows (older versions may work - we haven't tested.) - Visual Studio 2019 (or later) on Windows, with some caveats due to range-v3's strict conformance requirements: - range-v3 needs `/permissive-` and either `/std:c++latest`, `/std:c++20`, or `/std:c++17` **Development Status:** This code is fairly stable, well-tested, and suitable for casual use, although currently lacking documentation. _In general_, no promise is made about support or long-term stability. This code *will* evolve without regard to backwards compatibility. A notable exception is anything found within the `ranges::cpp20` namespace. Those components will change rarely or (preferably) never at all. **Build status** - on GitHub Actions: [![GitHub Actions Status](https://github.com/ericniebler/range-v3/workflows/range-v3%20CI/badge.svg?branch=master)](https://github.com/ericniebler/range-v3/actions) Building range-v3 - Using vcpkg ------------------------------- You can download and install range-v3 using the [vcpkg](https://github.com/Microsoft/vcpkg) dependency manager: git clone https://github.com/Microsoft/vcpkg.git cd vcpkg ./bootstrap-vcpkg.sh ./vcpkg integrate install ./vcpkg install range-v3 The range-v3 port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please [create an issue or pull request](https://github.com/Microsoft/vcpkg) on the vcpkg repository. Building range-v3 - Using Conan ------------------------------- You can download and install range-v3 using the [Conan](https://github.com/conan-io/conan) dependency manager. Setup your CMakeLists.txt (see [Conan documentation](https://docs.conan.io/en/latest/integrations/build_system.html) on how to use MSBuild, Meson and others): ``` project(myproject CXX) add_executable(${PROJECT_NAME} main.cpp) include(${CMAKE_BINARY_DIR}/conanbuildinfo.cmake) # Include Conan-generated file conan_basic_setup(TARGETS) # Introduce Conan-generated targets target_link_libraries(${PROJECT_NAME} CONAN_PKG::range-v3) ``` Create `conanfile.txt` in your source dir: ``` [requires] range-v3/0.12.0 [generators] cmake ``` Install and run `conan`, then build your project as always: ``` pip install conan mkdir build cd build conan install ../ --build=missing cmake ../ cmake --build . ``` Building range-v3 - Using `build2` ---------------------------------- You can use [`build2`](https://build2.org), a dependency manager and a build-system combined, to use `range-v3` (or work on it): Currently this package is available in these package repositories: - **https://cppget.org/range-v3/** for released and published versions. - [**The git repository with the sources of the `build2` package of `range-v3`**](https://github.com/build2-packaging/range-v3.git) for unreleased or custom revisions of `range-v3`, or for working on it with `build2`. ### Usage: - `build2` package name: `range-v3` - Library target name : `lib{range-v3}` - [Detailed use cases and instructions in this document](https://github.com/build2-packaging/range-v3/NOTES-build2.md). For example, to make your `build2` project depend on `range-v3`: - Add one of the repositories to your configurations, or in your `repositories.manifest`, if not already there; for example: ``` : role: prerequisite location: https://pkg.cppget.org/1/alpha # v0.11.0 is there. ``` - Add this package as a dependency to your `manifest` file (example for `v0.11.x`): ``` depends: range-v3 ~0.11.0 ``` - Import the target and use it as a prerequisite to your own target using `range-v3` in the appropriate `buildfile`: ``` import range_v3 = range-v3%lib{range-v3} lib{mylib} : cxx{**} ... $range_v3 ``` Then just build your project as usual (with `b` or `bdep update`), `build2` will figure out the rest. For `build2` newcomers or to get more details and use cases, you can read [this document](https://github.com/build2-packaging/range-v3/NOTES-build2.md) and the [`build2` toolchain introduction](https://build2.org/build2-toolchain/doc/build2-toolchain-intro.xhtml). Say Thanks! ----------- I do this work because I love it and because I love C++ and want it to be as excellent as I know it can be. If you like my work and are looking for a way to say thank you, you can leave a supportive comment on [my blog](http://ericniebler.com). Or you could leave me some kudos on my Open Hub range-v3 contribution page. Just click the **Give Kudos** button [here](https://www.openhub.net/p/range-v3/contributors/3053743222308608). range-v3-0.12.0/TODO.md000066400000000000000000000021531425443461700143160ustar00rootroot00000000000000* Add contiguous iterator utilities. How about `is_contiguous_iterator` and `as_contiguous_range`: ``` CPP_template(typename I, typename S)( requires RandomAccessIterator && SizedSentinel && is_contiguous_iterator()) subrange>> as_contiguous_range(I begin, S end) { if(begin == end) return {nullptr, nullptr}; else return {addressof(*begin), addressof(*begin) + (end - begin)}; } ``` * Longer-term goals: - Make `inplace_merge` work with forward iterators - Make the sorting algorithms work with forward iterators * Maybe iterators are not necessarily countable. Is there a relation between the ability to be able to subtract two iterators to find the distance, and with the existence of a DistanceType associated type? Think of: - counted iterators (subtractable regardless of traversal category) - repeat_view iterators (*not* subtractable but could be random access otherwise) - infinite ranges (only countable with an infinite precision integer which we lack) range-v3-0.12.0/Version.cmake000066400000000000000000000005201425443461700156520ustar00rootroot00000000000000# To update the range-v3 version, from a working directory that is clean except for an # updated doc/release_notes.md file, update the version numbers below. This makefile will # generate a new version.hpp, *AMEND THE MOST RECENT COMMIT*, and git-tag the commit. set(RANGE_V3_MAJOR 0) set(RANGE_V3_MINOR 12) set(RANGE_V3_PATCHLEVEL 0) range-v3-0.12.0/WORKSPACE000066400000000000000000000000001425443461700144750ustar00rootroot00000000000000range-v3-0.12.0/cmake/000077500000000000000000000000001425443461700143065ustar00rootroot00000000000000range-v3-0.12.0/cmake/GoogleBenchmark.cmake.in000066400000000000000000000012001425443461700207350ustar00rootroot00000000000000# Copyright Eric Niebler 2019 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) cmake_minimum_required(VERSION 2.8.2) project(google-benchmark-download NONE) include(ExternalProject) ExternalProject_Add(google-benchmark GIT_REPOSITORY https://github.com/google/benchmark.git GIT_TAG master SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/google-benchmark-src" BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/google-benchmark-build" CONFIGURE_COMMAND "" BUILD_COMMAND "" INSTALL_COMMAND "" TEST_COMMAND "" ) range-v3-0.12.0/cmake/GoogleTest.cmake.in000066400000000000000000000011551425443461700177730ustar00rootroot00000000000000# Copyright Eric Niebler 2019 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) cmake_minimum_required(VERSION 2.8.2) project(google-test-download NONE) include(ExternalProject) ExternalProject_Add(google-test GIT_REPOSITORY https://github.com/google/googletest.git GIT_TAG master SOURCE_DIR "${CMAKE_CURRENT_BINARY_DIR}/google-test-src" BINARY_DIR "${CMAKE_CURRENT_BINARY_DIR}/google-test-build" CONFIGURE_COMMAND "" BUILD_COMMAND "" INSTALL_COMMAND "" TEST_COMMAND "" ) range-v3-0.12.0/cmake/TestHeaders.cmake000066400000000000000000000112641425443461700175270ustar00rootroot00000000000000# Copyright Louis Dionne 2013-2017 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) # # # This CMake module provides a function generating a unit test to make sure # that every public header can be included on its own. # # When a C++ library or application has many header files, it can happen that # a header does not include all the other headers it depends on. When this is # the case, it can happen that including that header file on its own will # break the compilation. This CMake module generates a dummy executable # comprised of many .cpp files, each of which includes a header file that # is part of the public API. In other words, the executable is comprised # of .cpp files of the form: # # #include # # and then exactly one `main` function. If this succeeds to compile, it means # that the header can be included on its own, which is what clients expect. # Otherwise, you have a problem. Since writing these dumb unit tests by hand # is tedious and repetitive, you can use this CMake module to automate this # task. # add_header_test( [EXCLUDE_FROM_ALL] [EXCLUDE excludes...] HEADERS headers...) # # Generates header-inclusion unit tests for all the specified headers. # # This function creates a target which builds a dummy executable including # each specified header file individually. If this target builds successfully, # it means that all the specified header files can be included individually. # # Parameters # ---------- # : # The name of the target to generate. # # HEADERS headers: # A list of header files to generate the inclusion tests for. All headers # in this list must be represented as relative paths from the root of the # include directory added to the compiler's header search path. In other # words, it should be possible to include all headers in this list as # # #include <${header}> # # For example, for a library with the following structure: # # project/ # doc/ # test/ # ... # include/ # boost/ # hana.hpp # hana/ # transform.hpp # tuple.hpp # pair.hpp # ... # # When building the unit tests for that library, we'll add `-I project/include' # to the compiler's arguments. The list of public headers should therefore contain # # boost/hana.hpp # boost/hana/transform.hpp # boost/hana/tuple.hpp # boost/hana/pair.hpp # ... # # Usually, all the 'public' header files of a library should be tested for # standalone inclusion. A header is considered 'public' if a client should # be able to include that header on its own. # # [EXCLUDE excludes]: # An optional list of headers or regexes for which no unit test should be # generated. Basically, any header in the list specified by the `HEADERS` # argument that matches anything in `EXCLUDE` will be skipped. # # [EXCLUDE_FROM_ALL]: # If provided, the generated target is excluded from the 'all' target. # function(add_header_test target) cmake_parse_arguments(ARGS "EXCLUDE_FROM_ALL" # options "" # 1 value args "HEADERS;EXCLUDE" # multivalued args ${ARGN}) if (NOT ARGS_HEADERS) message(FATAL_ERROR "The `HEADERS` argument must be provided.") endif() if (ARGS_EXCLUDE_FROM_ALL) set(ARGS_EXCLUDE_FROM_ALL "EXCLUDE_FROM_ALL") else() set(ARGS_EXCLUDE_FROM_ALL "") endif() foreach(header ${ARGS_HEADERS}) set(skip FALSE) foreach(exclude ${ARGS_EXCLUDE}) if (${header} MATCHES ${exclude}) set(skip TRUE) break() endif() endforeach() if (skip) continue() endif() get_filename_component(filename "${header}" NAME_WE) get_filename_component(directory "${header}" DIRECTORY) set(source "${CMAKE_CURRENT_BINARY_DIR}/headers/${directory}/${filename}.cpp") if (NOT EXISTS "${source}") file(WRITE "${source}" "#include <${header}>") endif() list(APPEND sources "${source}") endforeach() set(standalone_main "${CMAKE_CURRENT_BINARY_DIR}/headers/_standalone_main.cpp") if (NOT EXISTS "${standalone_main}") file(WRITE "${standalone_main}" "int main() { }") endif() add_executable(${target} ${ARGS_EXCLUDE_FROM_ALL} ${sources} "${CMAKE_CURRENT_BINARY_DIR}/headers/_standalone_main.cpp" ) endfunction() range-v3-0.12.0/cmake/aligned_new_probe.cpp000066400000000000000000000002571425443461700204610ustar00rootroot00000000000000#include int main() { struct alignas(__STDCPP_DEFAULT_NEW_ALIGNMENT__ * 4) S {}; (void) ::operator new(sizeof(S), static_cast(alignof(S))); } range-v3-0.12.0/cmake/concepts_test_code.cpp000066400000000000000000000006261425443461700206650ustar00rootroot00000000000000#if !defined(__cpp_concepts) || __cpp_concepts == 0 #error "Sorry, Charlie. No concepts" #else #if __cpp_concepts <= 201507L #define concept concept bool #endif template concept True = true; template constexpr bool test(T) { return false; } template requires True constexpr bool test(T) { return true; } int main() { static_assert(::test(42), ""); } #endif range-v3-0.12.0/cmake/coro_test_code.cpp000066400000000000000000000021611425443461700200050ustar00rootroot00000000000000#if defined(__cpp_coroutines) && defined(__has_include) #if __has_include() #include namespace std_coro = std; #elif __has_include() #include namespace std_coro = std::experimental; #else #error Either the compiler or the library lacks support for coroutines #endif #else #error Either the compiler or the library lacks support for coroutines #endif struct present { struct promise_type { int result; present get_return_object() { return {*this}; } std_coro::suspend_never initial_suspend() { return {}; } std_coro::suspend_never final_suspend() noexcept { return {}; } void return_value(int i) { result = i; } void unhandled_exception() {} }; promise_type& promise; bool await_ready() const { return true; } void await_suspend(std_coro::coroutine_handle<>) const {} int await_resume() const { return promise.result; } }; present f(int n) { if (n < 2) co_return 1; else co_return n * co_await f(n - 1); } int main() { return f(5).promise.result != 120; } range-v3-0.12.0/cmake/gbenchmark.cmake000066400000000000000000000016431425443461700174150ustar00rootroot00000000000000# Download and unpack googletest at configure time configure_file( cmake/GoogleBenchmark.cmake.in google-benchmark-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G "${CMAKE_GENERATOR}" . RESULT_VARIABLE result WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/google-benchmark-download) if(result) message(FATAL_ERROR "CMake step for google-benchmark failed: ${result}") endif() execute_process(COMMAND ${CMAKE_COMMAND} --build . RESULT_VARIABLE result WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/google-benchmark-download) if(result) message(FATAL_ERROR "Build step for google-benchmark failed: ${result}") endif() # Add google-benchmark directly to our build. This defines # the benchmark and benchmark_main targets. add_subdirectory(${CMAKE_CURRENT_BINARY_DIR}/google-benchmark-src ${CMAKE_CURRENT_BINARY_DIR}/google-benchmark-build EXCLUDE_FROM_ALL) range-v3-0.12.0/cmake/gtest.cmake000066400000000000000000000022301425443461700164330ustar00rootroot00000000000000# Copyright 2019 Eric Niebler # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) # Download and unpack googletest at configure time configure_file(cmake/GoogleTest.cmake.in google-test-download/CMakeLists.txt) execute_process(COMMAND ${CMAKE_COMMAND} -G "${CMAKE_GENERATOR}" . RESULT_VARIABLE result WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/google-test-download ) if(result) message(FATAL_ERROR "CMake step for google-test failed: ${result}") endif() execute_process(COMMAND ${CMAKE_COMMAND} --build . RESULT_VARIABLE result WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/google-test-download ) if(result) message(FATAL_ERROR "Build step for google-test failed: ${result}") endif() # Prevent overriding the parent project's compiler/linker # settings on Windows set(gtest_force_shared_crt ON CACHE BOOL "" FORCE) # Add google-test directly to our build. This defines # the gtest and gtest_main targets. add_subdirectory(${CMAKE_CURRENT_BINARY_DIR}/google-test-src ${CMAKE_CURRENT_BINARY_DIR}/google-test-build EXCLUDE_FROM_ALL) range-v3-0.12.0/cmake/range-v3-config.cmake000066400000000000000000000016301425443461700201750ustar00rootroot00000000000000if (TARGET range-v3::meta) return() endif() include("${CMAKE_CURRENT_LIST_DIR}/range-v3-targets.cmake") add_library(range-v3::meta INTERFACE IMPORTED) add_library(range-v3::concepts INTERFACE IMPORTED) add_library(range-v3::range-v3 INTERFACE IMPORTED) # workaround for target_link_libraries on lower cmake versions (< 3.11) # see https://cmake.org/cmake/help/latest/release/3.11.html#commands if(CMAKE_VERSION VERSION_LESS 3.11) set_target_properties(range-v3::meta PROPERTIES INTERFACE_LINK_LIBRARIES "range-v3-meta") set_target_properties(range-v3::concepts PROPERTIES INTERFACE_LINK_LIBRARIES "range-v3-concepts") set_target_properties(range-v3::range-v3 PROPERTIES INTERFACE_LINK_LIBRARIES "range-v3") else() target_link_libraries(range-v3::meta INTERFACE range-v3-meta) target_link_libraries(range-v3::concepts INTERFACE range-v3-concepts) target_link_libraries(range-v3::range-v3 INTERFACE range-v3) endif() range-v3-0.12.0/cmake/ranges_diagnostics.cmake000066400000000000000000000041421425443461700211570ustar00rootroot00000000000000# Copyright Louis Dionne 2015 # Copyright Gonzalo Brito Gadeschi 2015 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) # # Setup compiler flags (more can be set on a per-target basis or in # subdirectories) # Enable all warnings: ranges_append_flag(RANGES_HAS_WEVERYTHING -Weverything) ranges_append_flag(RANGES_HAS_PEDANTIC -pedantic) ranges_append_flag(RANGES_HAS_PEDANTIC_ERRORS -pedantic-errors) # Selectively disable those warnings that are not worth it: ranges_append_flag(RANGES_HAS_WNO_CXX98_COMPAT -Wno-c++98-compat) ranges_append_flag(RANGES_HAS_WNO_CXX98_COMPAT_PEDANTIC -Wno-c++98-compat-pedantic) ranges_append_flag(RANGES_HAS_WNO_WEAK_VTABLES -Wno-weak-vtables) ranges_append_flag(RANGES_HAS_WNO_PADDED -Wno-padded) ranges_append_flag(RANGES_HAS_WNO_MISSING_VARIABLE_DECLARATIONS -Wno-missing-variable-declarations) ranges_append_flag(RANGES_HAS_WNO_DOCUMENTATION -Wno-documentation) ranges_append_flag(RANGES_HAS_WNO_DOCUMENTATION_UNKNOWN_COMMAND -Wno-documentation-unknown-command) ranges_append_flag(RANGES_HAS_WNO_OLD_STYLE_CAST -Wno-old-style-cast) if (RANGES_ENV_MACOSX) ranges_append_flag(RANGES_HAS_WNO_GLOBAL_CONSTRUCTORS -Wno-global-constructors) ranges_append_flag(RANGES_HAS_WNO_EXIT_TIME_DESTRUCTORS -Wno-exit-time-destructors) endif() if (RANGES_CXX_COMPILER_CLANG OR RANGES_CXX_COMPILER_CLANGCL) ranges_append_flag(RANGES_HAS_WNO_MISSING_PROTOTYPES -Wno-missing-prototypes) endif() if (RANGES_CXX_COMPILER_GCC) if (CMAKE_CXX_COMPILER_VERSION VERSION_LESS "6.0") ranges_append_flag(RANGES_HAS_WNO_STRICT_OVERFLOW -Wno-strict-overflow) if (CMAKE_CXX_COMPILER_VERSION VERSION_LESS "5.0") ranges_append_flag(RANGES_HAS_WNO_MISSING_FIELD_INITIALIZERS -Wno-missing-field-initializers) endif() elseif ((CMAKE_CXX_COMPILER_VERSION VERSION_GREATER "7.0") OR (CMAKE_CXX_COMPILER_VERSION VERSION_EQUAL "7.0")) ranges_append_flag(RANGES_HAS_WNO_NOEXCEPT_TYPE -Wno-noexcept-type) endif() endif() if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: test C++ flags: ${CMAKE_CXX_FLAGS}") endif() range-v3-0.12.0/cmake/ranges_env.cmake000066400000000000000000000053061425443461700174430ustar00rootroot00000000000000# Copyright Gonzalo Brito Gadeschi 2015 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) # # Detects the C++ compiler, system, build-type, etc. include(CheckCXXCompilerFlag) if("x${CMAKE_CXX_COMPILER_ID}" MATCHES "x.*Clang") if("x${CMAKE_CXX_SIMULATE_ID}" STREQUAL "xMSVC") set (RANGES_CXX_COMPILER_CLANGCL TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: compiler is clang-cl.") endif() else() set (RANGES_CXX_COMPILER_CLANG TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: compiler is clang.") endif() endif() elseif(CMAKE_COMPILER_IS_GNUCXX) set (RANGES_CXX_COMPILER_GCC TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: compiler is gcc.") endif() elseif("x${CMAKE_CXX_COMPILER_ID}" STREQUAL "xMSVC") set (RANGES_CXX_COMPILER_MSVC TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: compiler is msvc.") endif() else() message(WARNING "[range-v3 warning]: unknown compiler ${CMAKE_CXX_COMPILER_ID} !") endif() if(CMAKE_SYSTEM_NAME MATCHES "Darwin") set (RANGES_ENV_MACOSX TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: system is MacOSX.") endif() elseif(CMAKE_SYSTEM_NAME MATCHES "Linux") set (RANGES_ENV_LINUX TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: system is Linux.") endif() elseif(CMAKE_SYSTEM_NAME MATCHES "Windows") set (RANGES_ENV_WINDOWS TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: system is Windows.") endif() elseif(CMAKE_SYSTEM_NAME MATCHES "OpenBSD") set (RANGES_ENV_OPENBSD TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: system is OpenBSD.") endif() else() message(WARNING "[range-v3 warning]: unknown system ${CMAKE_SYSTEM_NAME} !") endif() if(RANGES_CXX_STD MATCHES "^[0-9]+$") if(RANGES_CXX_COMPILER_MSVC AND RANGES_CXX_STD LESS 17) # MSVC is currently supported only in 17+ mode set(RANGES_CXX_STD 17) elseif(RANGES_CXX_STD LESS 14) set(RANGES_CXX_STD 14) endif() endif() # Build type set(RANGES_DEBUG_BUILD FALSE) set(RANGES_RELEASE_BUILD FALSE) if (CMAKE_BUILD_TYPE STREQUAL "Debug") set(RANGES_DEBUG_BUILD TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: build type is debug.") endif() elseif(CMAKE_BUILD_TYPE STREQUAL "Release") set(RANGES_RELEASE_BUILD TRUE) if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: build type is release.") endif() else() message(WARNING "[range-v3 warning]: unknown build type, defaults to release!") set(CMAKE_BUILD_TYPE "Release") set(RANGES_RELEASE_BUILD TRUE) endif() if(RANGE_V3_DOCS) find_package(Doxygen) endif() find_package(Git) range-v3-0.12.0/cmake/ranges_flags.cmake000066400000000000000000000304471425443461700177530ustar00rootroot00000000000000# Copyright Louis Dionne 2015 # Copyright Gonzalo Brito Gadeschi 2015 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) # # Setup compiler flags (more can be set on a per-target basis or in # subdirectories) # Compilation flags include(CheckCXXCompilerFlag) macro(ranges_append_flag testname flag) # As -Wno-* flags do not lead to build failure when there are no other # diagnostics, we check positive option to determine their applicability. # Of course, we set the original flag that is requested in the parameters. string(REGEX REPLACE "^-Wno-" "-W" alt ${flag}) check_cxx_compiler_flag(${alt} ${testname}) if (${testname}) add_compile_options(${flag}) endif() endmacro() function(cxx_standard_normalize cxx_standard return_value) if("x${cxx_standard}" STREQUAL "x1y") set( ${return_value} "14" PARENT_SCOPE ) elseif("x${cxx_standard}" STREQUAL "x1z") set( ${return_value} "17" PARENT_SCOPE ) elseif("x${cxx_standard}" STREQUAL "xlatest" OR "x${cxx_standard}" STREQUAL "x2a") set( ${return_value} "20" PARENT_SCOPE ) else() set( ${return_value} "${cxx_standard}" PARENT_SCOPE ) endif() endfunction() function(cxx_standard_denormalize cxx_standard return_value) if("x${cxx_standard}" STREQUAL "x17") if (RANGES_CXX_COMPILER_CLANGCL OR RANGES_CXX_COMPILER_MSVC) set( ${return_value} 17 PARENT_SCOPE ) else() set( ${return_value} 1z PARENT_SCOPE ) endif() elseif("x${cxx_standard}" STREQUAL "x20") if (RANGES_CXX_COMPILER_CLANGCL OR RANGES_CXX_COMPILER_MSVC) set( ${return_value} latest PARENT_SCOPE ) else() set( ${return_value} 2a PARENT_SCOPE ) endif() else() set( ${return_value} ${cxx_standard} PARENT_SCOPE ) endif() endfunction() if(CMAKE_CXX_STANDARD) if(NOT "x${RANGES_CXX_STD}" STREQUAL "xdefault") # Normalize RANGES_CXX_STD cxx_standard_normalize( ${RANGES_CXX_STD} ranges_cxx_std ) if(NOT "x${ranges_cxx_std}" STREQUAL "x${CMAKE_CXX_STANDARD}") message(FATAL_ERROR "[range-v3]: Cannot specify both CMAKE_CXX_STANDARD and RANGES_CXX_STD, or they must match.") endif() else() cxx_standard_denormalize(${CMAKE_CXX_STANDARD} RANGES_CXX_STD) endif() elseif("x${RANGES_CXX_STD}" STREQUAL "xdefault") if (RANGES_CXX_COMPILER_CLANGCL OR RANGES_CXX_COMPILER_MSVC) set(RANGES_CXX_STD 17) else() set(RANGES_CXX_STD 14) endif() endif() # All compilation flags # Language flag: version of the C++ standard to use message(STATUS "[range-v3]: C++ std=${RANGES_CXX_STD}") if (RANGES_CXX_COMPILER_CLANGCL OR RANGES_CXX_COMPILER_MSVC) ranges_append_flag(RANGES_HAS_CXXSTDCOLON "/std:c++${RANGES_CXX_STD}") set(RANGES_STD_FLAG "/std:c++${RANGES_CXX_STD}") if (RANGES_CXX_COMPILER_CLANGCL) # The MSVC STL before VS 2019v16.6 with Clang 10 requires -fms-compatibility in C++17 mode, and # doesn't support C++20 mode at all. Let's drop this flag until AppVeyor updates to VS2016v16.6. # ranges_append_flag(RANGES_HAS_FNO_MS_COMPATIBIILITY "-fno-ms-compatibility") ranges_append_flag(RANGES_HAS_FNO_DELAYED_TEMPLATE_PARSING "-fno-delayed-template-parsing") endif() # Enable "normal" warnings and make them errors: ranges_append_flag(RANGES_HAS_W3 /W3) ranges_append_flag(RANGES_HAS_WX /WX) else() ranges_append_flag(RANGES_HAS_CXXSTD "-std=c++${RANGES_CXX_STD}") set(RANGES_STD_FLAG "-std=c++${RANGES_CXX_STD}") # Enable "normal" warnings and make them errors: ranges_append_flag(RANGES_HAS_WALL -Wall) ranges_append_flag(RANGES_HAS_WEXTRA -Wextra) if (RANGES_ENABLE_WERROR) ranges_append_flag(RANGES_HAS_WERROR -Werror) endif() endif() if (RANGES_ENV_LINUX AND RANGES_CXX_COMPILER_CLANG) # On linux libc++ re-exports the system math headers. The ones from libstdc++ # use the GCC __extern_always_inline intrinsic which is not supported by clang # versions 3.6, 3.7, 3.8, 3.9, 4.0, and current trunk 5.0 (as of 2017.04.13). # # This works around it by replacing __extern_always_inline with inline using a # macro: ranges_append_flag(RANGES_HAS_D__EXTERN_ALWAYS_INLINE -D__extern_always_inline=inline) endif() # Deep integration support if (RANGES_DEEP_STL_INTEGRATION) if (RANGES_CXX_COMPILER_MSVC) add_compile_options(/I "${PROJECT_SOURCE_DIR}/include/std") add_compile_options(/I "${PROJECT_SOURCE_DIR}/include") else() add_compile_options(-isystem "${PROJECT_SOURCE_DIR}/include/std") add_compile_options(-I "${PROJECT_SOURCE_DIR}/include") endif() add_compile_options(-DRANGES_DEEP_STL_INTEGRATION=1) endif() # Template diagnostic flags ranges_append_flag(RANGES_HAS_FDIAGNOSTIC_SHOW_TEMPLATE_TREE -fdiagnostics-show-template-tree) ranges_append_flag(RANGES_HAS_FTEMPLATE_BACKTRACE_LIMIT "-ftemplate-backtrace-limit=0") ranges_append_flag(RANGES_HAS_FMACRO_BACKTRACE_LIMIT "-fmacro-backtrace-limit=1") # Clang modules support if (RANGES_MODULES) ranges_append_flag(RANGES_HAS_MODULES -fmodules) ranges_append_flag(RANGES_HAS_MODULE_MAP_FILE "-fmodule-map-file=${PROJECT_SOURCE_DIR}/include/module.modulemap") ranges_append_flag(RANGES_HAS_MODULE_CACHE_PATH "-fmodules-cache-path=${PROJECT_BINARY_DIR}/module.cache") if (RANGES_LIBCXX_MODULE) ranges_append_flag(RANGES_HAS_LIBCXX_MODULE_MAP_FILE "-fmodule-map-file=${RANGES_LIBCXX_MODULE}") endif() if (RANGES_ENV_MACOSX) ranges_append_flag(RANGES_HAS_NO_IMPLICIT_MODULE_MAPS -fno-implicit-module-maps) endif() if (RANGES_DEBUG_BUILD) ranges_append_flag(RANGES_HAS_GMODULES -gmodules) endif() endif() # Sanitizer support: detect incompatible sanitizer combinations if (RANGES_ASAN AND RANGES_MSAN) message(FATAL_ERROR "[range-v3 error]: AddressSanitizer and MemorySanitizer are both enabled at the same time!") endif() if (RANGES_MSAN AND RANGES_ENV_MACOSX) message(FATAL_ERROR "[range-v3 error]: MemorySanitizer is not supported on MacOSX!") endif() # AddressSanitizer support if (RANGES_ASAN) # This policy enables passing the linker flags to the linker when trying to # test the features, which is required to successfully link ASan binaries cmake_policy(SET CMP0056 NEW) set (ASAN_FLAGS "") if (RANGES_ENV_MACOSX) # LeakSanitizer not supported on MacOSX set (ASAN_FLAGS "-fsanitize=address,signed-integer-overflow,shift,integer-divide-by-zero,implicit-signed-integer-truncation,implicit-integer-sign-change,undefined,nullability") else() if (RANGES_CXX_COMPILER_CLANG AND CMAKE_CXX_COMPILER_VERSION VERSION_LESS "4.0") set (ASAN_FLAGS "-fsanitize=address") else() set (ASAN_FLAGS "-fsanitize=address,signed-integer-overflow,shift,integer-divide-by-zero,implicit-signed-integer-truncation,implicit-integer-sign-change,leak,nullability") endif() endif() ranges_append_flag(RANGES_HAS_ASAN "${ASAN_FLAGS}") if (RANGES_HAS_ASAN) #ASAN flags must be passed to the linker: set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} ${ASAN_FLAGS}") endif() ranges_append_flag(RANGES_HAS_SANITIZE_NO_RECOVER "-fno-sanitize-recover=all") ranges_append_flag(RANGES_HAS_NO_OMIT_FRAME_POINTER -fno-omit-frame-pointer) endif() # MemorySanitizer support if (RANGES_MSAN) # This policy enables passing the linker flags to the linker when trying to # compile the examples, which is required to successfully link MSan binaries cmake_policy(SET CMP0056 NEW) ranges_append_flag(RANGES_HAS_MSAN "-fsanitize=memory") ranges_append_flag(RANGES_HAS_MSAN_TRACK_ORIGINS -fsanitize-memory-track-origins) ranges_append_flag(RANGES_HAS_SANITIZE_RECOVER_ALL "-fno-sanitize-recover=all") ranges_append_flag(RANGES_HAS_NO_OMIT_FRAME_POINTER -fno-omit-frame-pointer) endif() # Build types: if (RANGES_DEBUG_BUILD AND RANGES_RELEASE_BUILD) message(FATAL_ERROR "[range-v3 error] Cannot simultaneously generate debug and release builds!") endif() if (RANGES_DEBUG_BUILD) ranges_append_flag(RANGES_HAS_NO_INLINE -fno-inline) ranges_append_flag(RANGES_HAS_STACK_PROTECTOR_ALL -fstack-protector-all) ranges_append_flag(RANGES_HAS_G3 -g3) # Clang can generate debug info tuned for LLDB or GDB if (RANGES_CXX_COMPILER_CLANG) if (RANGES_ENV_MACOSX) ranges_append_flag(RANGES_HAS_GLLDB -glldb) elseif(RANGES_ENV_LINUX OR RANGES_ENV_OPENBSD) ranges_append_flag(RANGES_HAS_GGDB -ggdb) endif() endif() endif() if (RANGES_RELEASE_BUILD) if (NOT RANGES_ASSERTIONS) ranges_append_flag(RANGES_HAS_DNDEBUG -DNDEBUG) endif() if (NOT RANGES_ASAN AND NOT RANGES_MSAN) # The quality of ASan and MSan error messages suffers if we disable the # frame pointer, so leave it enabled when compiling with either of them: ranges_append_flag(RANGES_HAS_OMIT_FRAME_POINTER -fomit-frame-pointer) endif() ranges_append_flag(RANGES_HAS_OFAST -Ofast) if (NOT RANGES_HAS_OFAST) ranges_append_flag(RANGES_HAS_O2 -O2) endif() ranges_append_flag(RANGES_HAS_STRICT_ALIASING -fstrict-aliasing) ranges_append_flag(RANGES_HAS_STRICT_VTABLE_POINTERS -fstrict-vtable-pointers) ranges_append_flag(RANGES_HAS_FAST_MATH -ffast-math) ranges_append_flag(RANGES_HAS_VECTORIZE -fvectorize) if (NOT RANGES_ENV_MACOSX) # Sized deallocation is not available in MacOSX: ranges_append_flag(RANGES_HAS_SIZED_DEALLOCATION -fsized-deallocation) endif() if (RANGES_LLVM_POLLY) set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -mllvm -polly -mllvm -polly-vectorizer=stripmine") endif() if (RANGES_CXX_COMPILER_CLANG AND (NOT (RANGES_INLINE_THRESHOLD EQUAL -1))) set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -mllvm -inline-threshold=${RANGES_INLINE_THRESHOLD}") endif() endif() if (RANGES_NATIVE) ranges_append_flag(RANGES_HAS_MARCH_NATIVE "-march=native") ranges_append_flag(RANGES_HAS_MTUNE_NATIVE "-mtune=native") endif() include(CheckCXXSourceCompiles) set(CMAKE_REQUIRED_FLAGS ${RANGES_STD_FLAG}) # Probe for library and compiler support for aligned new file(READ "${CMAKE_CURRENT_SOURCE_DIR}/cmake/aligned_new_probe.cpp" RANGE_V3_PROBE_CODE) check_cxx_source_compiles("${RANGE_V3_PROBE_CODE}" RANGE_V3_ALIGNED_NEW_PROBE) unset(RANGE_V3_PROBE_CODE) unset(CMAKE_REQUIRED_FLAGS) if (NOT RANGE_V3_ALIGNED_NEW_PROBE) add_compile_options("-DRANGES_CXX_ALIGNED_NEW=0") endif() # Probe for coroutine TS support file(READ "${CMAKE_CURRENT_SOURCE_DIR}/cmake/coro_test_code.cpp" RANGE_V3_PROBE_CODE) if(RANGES_CXX_COMPILER_MSVC) set(CMAKE_REQUIRED_FLAGS "/await") check_cxx_source_compiles("${RANGE_V3_PROBE_CODE}" RANGES_HAS_AWAIT) if(RANGES_HAS_AWAIT) set(RANGE_V3_COROUTINE_FLAGS "/await") endif() elseif(RANGES_CXX_COMPILER_CLANG) set(CMAKE_REQUIRED_FLAGS "-fcoroutines-ts ${RANGES_STD_FLAG}") check_cxx_source_compiles("${RANGE_V3_PROBE_CODE}" RANGES_HAS_FCOROUTINES_TS) if(RANGES_HAS_FCOROUTINES_TS) set(RANGE_V3_COROUTINE_FLAGS "-fcoroutines-ts") endif() endif() unset(CMAKE_REQUIRED_FLAGS) unset(RANGE_V3_PROBE_CODE) if (RANGE_V3_COROUTINE_FLAGS) add_compile_options(${RANGE_V3_COROUTINE_FLAGS}) endif() # Test for concepts support file(READ "${CMAKE_CURRENT_SOURCE_DIR}/cmake/concepts_test_code.cpp" RANGE_V3_PROBE_CODE) if(RANGES_CXX_COMPILER_GCC OR RANGES_CXX_COMPILER_CLANG) set(CMAKE_REQUIRED_FLAGS "-fconcepts ${RANGES_STD_FLAG}") check_cxx_source_compiles("${RANGE_V3_PROBE_CODE}" RANGE_V3_HAS_FCONCEPTS) if(RANGE_V3_HAS_FCONCEPTS) set(RANGE_V3_CONCEPTS_FLAGS "-fconcepts") endif() endif() unset(CMAKE_REQUIRED_FLAGS) unset(RANGE_V3_PROBE_CODE) if (RANGE_V3_CONCEPTS_FLAGS AND RANGES_PREFER_REAL_CONCEPTS) add_compile_options(${RANGE_V3_CONCEPTS_FLAGS}) endif() if (RANGES_VERBOSE_BUILD) get_directory_property(RANGES_COMPILE_OPTIONS COMPILE_OPTIONS) message(STATUS "[range-v3]: C++ flags: ${CMAKE_CXX_FLAGS}") message(STATUS "[range-v3]: C++ debug flags: ${CMAKE_CXX_FLAGS_DEBUG}") message(STATUS "[range-v3]: C++ Release Flags: ${CMAKE_CXX_FLAGS_RELEASE}") message(STATUS "[range-v3]: C++ Compile Flags: ${CMAKE_CXX_COMPILE_FLAGS}") message(STATUS "[range-v3]: Compile options: ${RANGES_COMPILE_OPTIONS}") message(STATUS "[range-v3]: C Flags: ${CMAKE_C_FLAGS}") message(STATUS "[range-v3]: C Compile Flags: ${CMAKE_C_COMPILE_FLAGS}") message(STATUS "[range-v3]: EXE Linker flags: ${CMAKE_EXE_LINKER_FLAGS}") message(STATUS "[range-v3]: C++ Linker flags: ${CMAKE_CXX_LINK_FLAGS}") message(STATUS "[range-v3]: MODULE Linker flags: ${CMAKE_MODULE_LINKER_FLAGS}") get_directory_property(CMakeCompDirDefs COMPILE_DEFINITIONS) message(STATUS "[range-v3]: Compile Definitions: ${CmakeCompDirDefs}") endif() range-v3-0.12.0/cmake/ranges_options.cmake000066400000000000000000000041701425443461700203440ustar00rootroot00000000000000# Copyright Gonzalo Brito Gadeschi 2015 # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE.md or copy at http://boost.org/LICENSE_1_0.txt) # # CMake options include(CMakeDependentOption) set(RANGES_CXX_STD default CACHE STRING "C++ standard version.") option(RANGES_BUILD_CALENDAR_EXAMPLE "Builds the calendar example." ON) option(RANGES_ASAN "Run the tests using AddressSanitizer." OFF) option(RANGES_MSAN "Run the tests using MemorySanitizer." OFF) option(RANGES_ASSERTIONS "Enable assertions." ON) option(RANGES_DEBUG_INFO "Include debug information in the binaries." ON) option(RANGES_MODULES "Enables use of Clang modules (experimental)." OFF) option(RANGES_NATIVE "Enables -march/-mtune=native." ON) option(RANGES_VERBOSE_BUILD "Enables debug output from CMake." OFF) option(RANGES_LLVM_POLLY "Enables LLVM Polly." OFF) option(RANGES_ENABLE_WERROR "Enables -Werror. Only effective if compiler is not clang-cl or MSVC. ON by default" ON) option(RANGES_PREFER_REAL_CONCEPTS "Use real concepts instead of emulation if the compiler supports it" ON) option(RANGES_DEEP_STL_INTEGRATION "Hijacks the primary std::iterator_traits template to emulate the C++20 std::ranges:: behavior." OFF) option(RANGE_V3_HEADER_CHECKS "Build the Range-v3 header checks and integrate with ctest" OFF) set(RANGES_INLINE_THRESHOLD -1 CACHE STRING "Force a specific inlining threshold.") # Enable verbose configure when passing -Wdev to CMake if (DEFINED CMAKE_SUPPRESS_DEVELOPER_WARNINGS AND NOT CMAKE_SUPPRESS_DEVELOPER_WARNINGS) set(RANGES_VERBOSE_BUILD ON) endif() if (RANGES_VERBOSE_BUILD) message(STATUS "[range-v3]: verbose build enabled.") endif() CMAKE_DEPENDENT_OPTION(RANGE_V3_TESTS "Build the Range-v3 tests and integrate with ctest" ON "${is_standalone}" OFF) CMAKE_DEPENDENT_OPTION(RANGE_V3_EXAMPLES "Build the Range-v3 examples and integrate with ctest" ON "${is_standalone}" OFF) option(RANGE_V3_PERF "Build the Range-v3 performance benchmarks" OFF) CMAKE_DEPENDENT_OPTION(RANGE_V3_DOCS "Build the Range-v3 documentation" ON "${is_standalone}" OFF) mark_as_advanced(RANGE_V3_PERF) range-v3-0.12.0/cmake/readme.md000066400000000000000000000003501425443461700160630ustar00rootroot00000000000000# CMake files overview: - `ranges_options.cmake`: All options to configure the library. - `ranges_env.cmake`: Detects the environment: operating system, compiler, build-type, ... - `ranges_flags.cmake`: Sets up all compiler flags. range-v3-0.12.0/conanfile.py000066400000000000000000000024111425443461700155340ustar00rootroot00000000000000# Range v3 library # # Copyright Luis Martinez de Bartolome Izquierdo 2016 # # Use, modification and distribution is subject to the # Boost Software License, Version 1.0. (See accompanying # file LICENSE_1_0.txt or copy at # http://www.boost.org/LICENSE_1_0.txt) # # Project home: https://github.com/ericniebler/range-v3 # from conans import ConanFile, CMake class Rangev3Conan(ConanFile): name = "range-v3" version = "0.12.0" license = "Boost Software License - Version 1.0 - August 17th, 2003" url = "https://github.com/ericniebler/range-v3" description = """Experimental range library for C++14/17/20""" # No settings/options are necessary, this is header only exports_sources = "include*", "LICENSE.txt", "CMakeLists.txt", "cmake/*", "Version.cmake", "version.hpp.in" no_copy_source = True def package(self): cmake = CMake(self) cmake.definitions["RANGE_V3_TESTS"] = "OFF" cmake.definitions["RANGE_V3_EXAMPLES"] = "OFF" cmake.definitions["RANGE_V3_PERF"] = "OFF" cmake.definitions["RANGE_V3_DOCS"] = "OFF" cmake.definitions["RANGE_V3_HEADER_CHECKS"] = "OFF" cmake.configure() cmake.install() self.copy("LICENSE.txt", dst="licenses", ignore_case=True, keep_path=False) range-v3-0.12.0/doc/000077500000000000000000000000001425443461700137735ustar00rootroot00000000000000range-v3-0.12.0/doc/CMakeLists.txt000066400000000000000000000055721425443461700165440ustar00rootroot00000000000000#============================================================================= # Setup the documentation #============================================================================= if (NOT DOXYGEN_FOUND) message(STATUS "Doxygen not found; the 'range-v3-doc' and 'range-v3-gh-pages.{clean,copy,update}' targets " "will be unavailable.") return() endif() set(CMAKE_FOLDER "doc") configure_file(Doxyfile.in Doxyfile @ONLY) configure_file(preprocess.sh.in preprocess.sh @ONLY) add_custom_target(range.v3.doc.check COMMAND ${DOXYGEN_EXECUTABLE} Doxyfile COMMENT "Running Doxygen to validate the documentation" VERBATIM ) set_target_properties(range.v3.doc.check PROPERTIES FOLDER ${CMAKE_FOLDER} ) # if (NOT TARGET benchmarks) # message(STATUS # "The 'benchmarks' target is not available; the 'doc' and " # "'gh-pages.{clean,copy,update}' targets will be unavailable. " # "The 'doc.check' target can still be used to generate the " # "documentation to check for errors/warnings.") # return() # endif() add_custom_target(range-v3-doc COMMAND ${DOXYGEN_EXECUTABLE} Doxyfile COMMENT "Generating API documentation with Doxygen" # DEPENDS range-v3-benchmarks VERBATIM ) set_target_properties(range-v3-doc PROPERTIES FOLDER ${CMAKE_FOLDER} ) if (NOT GIT_FOUND) message(STATUS "Git was not found; the 'range-v3-gh-pages.{clean,copy,update}' targets " "will be unavailable.") return() endif() add_custom_target(range-v3-gh-pages.clean COMMAND ${CMAKE_COMMAND} -P ${CMAKE_CURRENT_LIST_DIR}/clean-gh-pages.cmake COMMAND ${CMAKE_COMMAND} -E remove_directory search WORKING_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}/gh-pages COMMENT "Cleaning up doc/gh-pages" VERBATIM ) set_target_properties(range-v3-gh-pages.clean PROPERTIES FOLDER ${CMAKE_FOLDER} ) add_custom_target(range-v3-gh-pages.copy COMMAND ${CMAKE_COMMAND} -E copy_directory ${CMAKE_CURRENT_BINARY_DIR}/html ${CMAKE_CURRENT_LIST_DIR}/gh-pages WORKING_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}/gh-pages COMMENT "Copying the documentation from ${CMAKE_CURRENT_BINARY_DIR}/html to doc/gh-pages" DEPENDS range-v3-doc range-v3-gh-pages.clean VERBATIM ) set_target_properties(range-v3-gh-pages.copy PROPERTIES FOLDER ${CMAKE_FOLDER} ) execute_process( COMMAND ${GIT_EXECUTABLE} -C ${CMAKE_SOURCE_DIR} rev-parse --short HEAD OUTPUT_VARIABLE RANGE_V3_GIT_SHORT_SHA OUTPUT_STRIP_TRAILING_WHITESPACE ) add_custom_target(range-v3-gh-pages.update COMMAND ${GIT_EXECUTABLE} add --all . COMMAND ${GIT_EXECUTABLE} commit -m "Update to ${RANGE_V3_GIT_SHORT_SHA}" WORKING_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}/gh-pages COMMENT "Updating the gh-pages branch with freshly built documentation" DEPENDS range-v3-gh-pages.copy VERBATIM ) set_target_properties(range-v3-gh-pages.update PROPERTIES FOLDER ${CMAKE_FOLDER} ) range-v3-0.12.0/doc/Doxyfile.in000066400000000000000000003610751425443461700161220ustar00rootroot00000000000000# Doxyfile 1.9.4 # This file describes the settings to be used by the documentation system # doxygen (www.doxygen.org) for a project. # # All text after a double hash (##) is considered a comment and is placed in # front of the TAG it is preceding. # # All text after a single hash (#) is considered a comment and will be ignored. # The format is: # TAG = value [value, ...] # For lists, items can also be appended using: # TAG += value [value, ...] # Values that contain spaces should be placed between quotes (\" \"). # # Note: # # Use doxygen to compare the used configuration file with the template # configuration file: # doxygen -x [configFile] # Use doxygen to compare the used configuration file with the template # configuration file without replacing the environment variables: # doxygen -x_noenv [configFile] #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- # This tag specifies the encoding used for all characters in the configuration # file that follow. The default is UTF-8 which is also the encoding used for all # text before the first occurrence of this tag. Doxygen uses libiconv (or the # iconv built into libc) for the transcoding. See # https://www.gnu.org/software/libiconv/ for the list of possible encodings. # The default value is: UTF-8. DOXYFILE_ENCODING = UTF-8 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by # double-quotes, unless you are using Doxywizard) that should identify the # project for which the documentation is generated. This name is used in the # title of most generated pages and in a few other places. # The default value is: My Project. PROJECT_NAME = Range-v3 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This # could be handy for archiving the generated documentation or if some version # control system is used. PROJECT_NUMBER = # Using the PROJECT_BRIEF tag one can provide an optional one line description # for a project that appears at the top of each page and should give viewer a # quick idea about the purpose of the project. Keep the description short. PROJECT_BRIEF = "Range algorithms, views, and actions for the Standard Library" # With the PROJECT_LOGO tag one can specify a logo or an icon that is included # in the documentation. The maximum height of the logo should not exceed 55 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy # the logo to the output directory. PROJECT_LOGO = # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path # into which the generated documentation will be written. If a relative path is # entered, it will be relative to the location where doxygen was started. If # left blank the current directory will be used. OUTPUT_DIRECTORY = # If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096 # sub-directories (in 2 levels) under the output directory of each output format # and will distribute the generated files over these directories. Enabling this # option can be useful when feeding doxygen a huge amount of source files, where # putting all generated files in the same directory would otherwise causes # performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to # control the number of sub-directories. # The default value is: NO. CREATE_SUBDIRS = NO # Controls the number of sub-directories that will be created when # CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every # level increment doubles the number of directories, resulting in 4096 # directories at level 8 which is the default and also the maximum value. The # sub-directories are organized in 2 levels, the first level always has a fixed # numer of 16 directories. # Minimum value: 0, maximum value: 8, default value: 8. # This tag requires that the tag CREATE_SUBDIRS is set to YES. CREATE_SUBDIRS_LEVEL = 8 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII # characters to appear in the names of generated files. If set to NO, non-ASCII # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode # U+3044. # The default value is: NO. ALLOW_UNICODE_NAMES = NO # The OUTPUT_LANGUAGE tag is used to specify the language in which all # documentation generated by doxygen is written. Doxygen will use this # information to generate all constant output in the proper language. # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian, # Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English # (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek, # Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with # English messages), Korean, Korean-en (Korean with English messages), Latvian, # Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, # Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, # Swedish, Turkish, Ukrainian and Vietnamese. # The default value is: English. OUTPUT_LANGUAGE = English # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member # descriptions after the members that are listed in the file and class # documentation (similar to Javadoc). Set to NO to disable this. # The default value is: YES. BRIEF_MEMBER_DESC = YES # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief # description of a member or function before the detailed description # # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the # brief descriptions will be completely suppressed. # The default value is: YES. REPEAT_BRIEF = YES # This tag implements a quasi-intelligent brief description abbreviator that is # used to form the text in various listings. Each string in this list, if found # as the leading text of the brief description, will be stripped from the text # and the result, after processing the whole list, is used as the annotated # text. Otherwise, the brief description is used as-is. If left blank, the # following values are used ($name is automatically replaced with the name of # the entity):The $name class, The $name widget, The $name file, is, provides, # specifies, contains, represents, a, an and the. ABBREVIATE_BRIEF = "The $name class" \ "The $name widget" \ "The $name file" \ is \ provides \ specifies \ contains \ represents \ a \ an \ the # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then # doxygen will generate a detailed section even if there is only a brief # description. # The default value is: NO. ALWAYS_DETAILED_SEC = NO # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all # inherited members of a class in the documentation of that class as if those # members were ordinary class members. Constructors, destructors and assignment # operators of the base classes will not be shown. # The default value is: NO. INLINE_INHERITED_MEMB = NO # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path # before files name in the file list and in the header files. If set to NO the # shortest path that makes the file name unique will be used # The default value is: YES. FULL_PATH_NAMES = YES # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. # Stripping is only done if one of the specified strings matches the left-hand # part of the path. The tag can be used to show relative paths in the file list. # If left blank the directory from which doxygen is run is used as the path to # strip. # # Note that you can specify absolute paths here, but also relative paths, which # will be relative from the directory where doxygen is started. # This tag requires that the tag FULL_PATH_NAMES is set to YES. STRIP_FROM_PATH = @Range-v3_SOURCE_DIR@/include \ @Range-v3_SOURCE_DIR@/doc # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the # path mentioned in the documentation of a class, which tells the reader which # header file to include in order to use a class. If left blank only the name of # the header file containing the class definition is used. Otherwise one should # specify the list of include paths that are normally passed to the compiler # using the -I flag. STRIP_FROM_INC_PATH = @Range-v3_SOURCE_DIR@/include # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but # less readable) file names. This can be useful is your file systems doesn't # support long names like on DOS, Mac, or CD-ROM. # The default value is: NO. SHORT_NAMES = NO # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the # first line (until the first dot) of a Javadoc-style comment as the brief # description. If set to NO, the Javadoc-style will behave just like regular Qt- # style comments (thus requiring an explicit @brief command for a brief # description.) # The default value is: NO. JAVADOC_AUTOBRIEF = YES # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line # such as # /*************** # as being the beginning of a Javadoc-style comment "banner". If set to NO, the # Javadoc-style will behave just like regular comments and it will not be # interpreted by doxygen. # The default value is: NO. JAVADOC_BANNER = NO # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first # line (until the first dot) of a Qt-style comment as the brief description. If # set to NO, the Qt-style will behave just like regular Qt-style comments (thus # requiring an explicit \brief command for a brief description.) # The default value is: NO. QT_AUTOBRIEF = YES # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a # multi-line C++ special comment block (i.e. a block of //! or /// comments) as # a brief description. This used to be the default behavior. The new default is # to treat a multi-line C++ comment block as a detailed description. Set this # tag to YES if you prefer the old behavior instead. # # Note that setting this tag to YES also means that rational rose comments are # not recognized any more. # The default value is: NO. MULTILINE_CPP_IS_BRIEF = YES # By default Python docstrings are displayed as preformatted text and doxygen's # special commands cannot be used. By setting PYTHON_DOCSTRING to NO the # doxygen's special commands can be used and the contents of the docstring # documentation blocks is shown as doxygen documentation. # The default value is: YES. PYTHON_DOCSTRING = YES # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the # documentation from any documented member that it re-implements. # The default value is: YES. INHERIT_DOCS = NO # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new # page for each member. If set to NO, the documentation of a member will be part # of the file/class/namespace that contains it. # The default value is: NO. SEPARATE_MEMBER_PAGES = NO # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen # uses this value to replace tabs by spaces in code fragments. # Minimum value: 1, maximum value: 16, default value: 4. TAB_SIZE = 4 # This tag can be used to specify a number of aliases that act as commands in # the documentation. An alias has the form: # name=value # For example adding # "sideeffect=@par Side Effects:^^" # will allow you to put the command \sideeffect (or @sideeffect) in the # documentation, which will result in a user-defined paragraph with heading # "Side Effects:". Note that you cannot put \n's in the value part of an alias # to insert newlines (in the resulting output). You can put ^^ in the value part # of an alias to insert a newline as if a physical newline was in the original # file. When you need a literal { or } or , in the value part of an alias you # have to escape them by means of a backslash (\), this can lead to conflicts # with the commands \{ and \} for these it is advised to use the version @{ and # @} or use a double escape (\\{ and \\}) ALIASES = # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources # only. Doxygen will then generate output that is more tailored for C. For # instance, some of the names that are used will be different. The list of all # members will be omitted, etc. # The default value is: NO. OPTIMIZE_OUTPUT_FOR_C = NO # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or # Python sources only. Doxygen will then generate output that is more tailored # for that language. For instance, namespaces will be presented as packages, # qualified scopes will look different, etc. # The default value is: NO. OPTIMIZE_OUTPUT_JAVA = NO # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran # sources. Doxygen will then generate output that is tailored for Fortran. # The default value is: NO. OPTIMIZE_FOR_FORTRAN = NO # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for VHDL. # The default value is: NO. OPTIMIZE_OUTPUT_VHDL = NO # Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice # sources only. Doxygen will then generate output that is more tailored for that # language. For instance, namespaces will be presented as modules, types will be # separated into more groups, etc. # The default value is: NO. OPTIMIZE_OUTPUT_SLICE = NO # Doxygen selects the parser to use depending on the extension of the files it # parses. With this tag you can assign which parser to use for a given # extension. Doxygen has a built-in mapping, but you can override or extend it # using this tag. The format is ext=language, where ext is a file extension, and # language is one of the parsers supported by doxygen: IDL, Java, JavaScript, # Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice, # VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran: # FortranFree, unknown formatted Fortran: Fortran. In the later case the parser # tries to guess whether the code is fixed or free formatted code, this is the # default for Fortran type files). For instance to make doxygen treat .inc files # as Fortran files (default is PHP), and .f files as C (default is Fortran), # use: inc=Fortran f=C. # # Note: For files without extension you can use no_extension as a placeholder. # # Note that for custom extensions you also need to set FILE_PATTERNS otherwise # the files are not read by doxygen. When specifying no_extension you should add # * to the FILE_PATTERNS. # # Note see also the list of default file extension mappings. EXTENSION_MAPPING = # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments # according to the Markdown format, which allows for more readable # documentation. See https://daringfireball.net/projects/markdown/ for details. # The output of markdown processing is further processed by doxygen, so you can # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in # case of backward compatibilities issues. # The default value is: YES. MARKDOWN_SUPPORT = YES # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up # to that level are automatically included in the table of contents, even if # they do not have an id attribute. # Note: This feature currently applies only to Markdown headings. # Minimum value: 0, maximum value: 99, default value: 5. # This tag requires that the tag MARKDOWN_SUPPORT is set to YES. TOC_INCLUDE_HEADINGS = 5 # When enabled doxygen tries to link words that correspond to documented # classes, or namespaces to their corresponding documentation. Such a link can # be prevented in individual cases by putting a % sign in front of the word or # globally by setting AUTOLINK_SUPPORT to NO. # The default value is: YES. AUTOLINK_SUPPORT = YES # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want # to include (a tag file for) the STL sources as input, then you should set this # tag to YES in order to let doxygen match functions declarations and # definitions whose arguments contain STL classes (e.g. func(std::string); # versus func(std::string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. # The default value is: NO. BUILTIN_STL_SUPPORT = YES # If you use Microsoft's C++/CLI language, you should set this option to YES to # enable parsing support. # The default value is: NO. CPP_CLI_SUPPORT = NO # Set the SIP_SUPPORT tag to YES if your project consists of sip (see: # https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen # will parse them like normal C++ but will assume all classes use public instead # of private inheritance when no explicit protection keyword is present. # The default value is: NO. SIP_SUPPORT = NO # For Microsoft's IDL there are propget and propput attributes to indicate # getter and setter methods for a property. Setting this option to YES will make # doxygen to replace the get and set methods by a property in the documentation. # This will only work if the methods are indeed getting or setting a simple # type. If this is not the case, or you want to show the methods anyway, you # should set this option to NO. # The default value is: YES. IDL_PROPERTY_SUPPORT = YES # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC # tag is set to YES then doxygen will reuse the documentation of the first # member in the group (if any) for the other members of the group. By default # all members of a group must be documented explicitly. # The default value is: NO. DISTRIBUTE_GROUP_DOC = NO # If one adds a struct or class to a group and this option is enabled, then also # any nested class or struct is added to the same group. By default this option # is disabled and one has to add nested compounds explicitly via \ingroup. # The default value is: NO. GROUP_NESTED_COMPOUNDS = NO # Set the SUBGROUPING tag to YES to allow class member groups of the same type # (for instance a group of public functions) to be put as a subgroup of that # type (e.g. under the Public Functions section). Set it to NO to prevent # subgrouping. Alternatively, this can be done per class using the # \nosubgrouping command. # The default value is: YES. SUBGROUPING = NO # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions # are shown inside the group in which they are included (e.g. using \ingroup) # instead of on a separate page (for HTML and Man pages) or section (for LaTeX # and RTF). # # Note that this feature does not work in combination with # SEPARATE_MEMBER_PAGES. # The default value is: NO. INLINE_GROUPED_CLASSES = NO # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions # with only public data fields or simple typedef fields will be shown inline in # the documentation of the scope in which they are defined (i.e. file, # namespace, or group documentation), provided this scope is documented. If set # to NO, structs, classes, and unions are shown on a separate page (for HTML and # Man pages) or section (for LaTeX and RTF). # The default value is: NO. INLINE_SIMPLE_STRUCTS = NO # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or # enum is documented as struct, union, or enum with the name of the typedef. So # typedef struct TypeS {} TypeT, will appear in the documentation as a struct # with name TypeT. When disabled the typedef will appear as a member of a file, # namespace, or class. And the struct will be named TypeS. This can typically be # useful for C code in case the coding convention dictates that all compound # types are typedef'ed and only the typedef is referenced, never the tag name. # The default value is: NO. TYPEDEF_HIDES_STRUCT = NO # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This # cache is used to resolve symbols given their name and scope. Since this can be # an expensive process and often the same symbol appears multiple times in the # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small # doxygen will become slower. If the cache is too large, memory is wasted. The # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 # symbols. At the end of a run doxygen will report the cache usage and suggest # the optimal cache size from a speed point of view. # Minimum value: 0, maximum value: 9, default value: 0. LOOKUP_CACHE_SIZE = 0 # The NUM_PROC_THREADS specifies the number of threads doxygen is allowed to use # during processing. When set to 0 doxygen will based this on the number of # cores available in the system. You can set it explicitly to a value larger # than 0 to get more control over the balance between CPU load and processing # speed. At this moment only the input processing can be done using multiple # threads. Since this is still an experimental feature the default is set to 1, # which effectively disables parallel processing. Please report any issues you # encounter. Generating dot graphs in parallel is controlled by the # DOT_NUM_THREADS setting. # Minimum value: 0, maximum value: 32, default value: 1. NUM_PROC_THREADS = 1 #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in # documentation are documented, even if no documentation was available. Private # class members and static file members will be hidden unless the # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. # Note: This will also disable the warnings about undocumented members that are # normally produced when WARNINGS is set to YES. # The default value is: NO. EXTRACT_ALL = NO # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will # be included in the documentation. # The default value is: NO. EXTRACT_PRIVATE = NO # If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual # methods of a class will be included in the documentation. # The default value is: NO. EXTRACT_PRIV_VIRTUAL = NO # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal # scope will be included in the documentation. # The default value is: NO. EXTRACT_PACKAGE = NO # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be # included in the documentation. # The default value is: NO. EXTRACT_STATIC = NO # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined # locally in source files will be included in the documentation. If set to NO, # only classes defined in header files are included. Does not have any effect # for Java sources. # The default value is: YES. EXTRACT_LOCAL_CLASSES = YES # This flag is only useful for Objective-C code. If set to YES, local methods, # which are defined in the implementation section but not in the interface are # included in the documentation. If set to NO, only methods in the interface are # included. # The default value is: NO. EXTRACT_LOCAL_METHODS = NO # If this flag is set to YES, the members of anonymous namespaces will be # extracted and appear in the documentation as a namespace called # 'anonymous_namespace{file}', where file will be replaced with the base name of # the file that contains the anonymous namespace. By default anonymous namespace # are hidden. # The default value is: NO. EXTRACT_ANON_NSPACES = NO # If this flag is set to YES, the name of an unnamed parameter in a declaration # will be determined by the corresponding definition. By default unnamed # parameters remain unnamed in the output. # The default value is: YES. RESOLVE_UNNAMED_PARAMS = YES # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all # undocumented members inside documented classes or files. If set to NO these # members will be included in the various overviews, but no documentation # section is generated. This option has no effect if EXTRACT_ALL is enabled. # The default value is: NO. HIDE_UNDOC_MEMBERS = NO # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all # undocumented classes that are normally visible in the class hierarchy. If set # to NO, these classes will be included in the various overviews. This option # has no effect if EXTRACT_ALL is enabled. # The default value is: NO. HIDE_UNDOC_CLASSES = NO # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend # declarations. If set to NO, these declarations will be included in the # documentation. # The default value is: NO. HIDE_FRIEND_COMPOUNDS = NO # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any # documentation blocks found inside the body of a function. If set to NO, these # blocks will be appended to the function's detailed documentation block. # The default value is: NO. HIDE_IN_BODY_DOCS = NO # The INTERNAL_DOCS tag determines if documentation that is typed after a # \internal command is included. If the tag is set to NO then the documentation # will be excluded. Set it to YES to include the internal documentation. # The default value is: NO. INTERNAL_DOCS = NO # With the correct setting of option CASE_SENSE_NAMES doxygen will better be # able to match the capabilities of the underlying filesystem. In case the # filesystem is case sensitive (i.e. it supports files in the same directory # whose names only differ in casing), the option must be set to YES to properly # deal with such files in case they appear in the input. For filesystems that # are not case sensitive the option should be set to NO to properly deal with # output files written for symbols that only differ in casing, such as for two # classes, one named CLASS and the other named Class, and to also support # references to files without having to specify the exact matching casing. On # Windows (including Cygwin) and MacOS, users should typically set this option # to NO, whereas on Linux or other Unix flavors it should typically be set to # YES. # The default value is: system dependent. CASE_SENSE_NAMES = YES # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with # their full class and namespace scopes in the documentation. If set to YES, the # scope will be hidden. # The default value is: NO. HIDE_SCOPE_NAMES = NO # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will # append additional text to a page's title, such as Class Reference. If set to # YES the compound reference will be hidden. # The default value is: NO. HIDE_COMPOUND_REFERENCE= NO # If the SHOW_HEADERFILE tag is set to YES then the documentation for a class # will show which file needs to be included to use the class. # The default value is: YES. SHOW_HEADERFILE = YES # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of # the files that are included by a file in the documentation of that file. # The default value is: YES. SHOW_INCLUDE_FILES = NO # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each # grouped member an include statement to the documentation, telling the reader # which file to include in order to use the member. # The default value is: NO. SHOW_GROUPED_MEMB_INC = YES # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include # files with double quotes in the documentation rather than with sharp brackets. # The default value is: NO. FORCE_LOCAL_INCLUDES = NO # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the # documentation for inline members. # The default value is: YES. INLINE_INFO = NO # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the # (detailed) documentation of file and class members alphabetically by member # name. If set to NO, the members will appear in declaration order. # The default value is: YES. SORT_MEMBER_DOCS = YES # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief # descriptions of file, namespace and class members alphabetically by member # name. If set to NO, the members will appear in declaration order. Note that # this will also influence the order of the classes in the class list. # The default value is: NO. SORT_BRIEF_DOCS = YES # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the # (brief and detailed) documentation of class members so that constructors and # destructors are listed first. If set to NO the constructors will appear in the # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief # member documentation. # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting # detailed member documentation. # The default value is: NO. SORT_MEMBERS_CTORS_1ST = NO # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy # of group names into alphabetical order. If set to NO the group names will # appear in their defined order. # The default value is: NO. SORT_GROUP_NAMES = NO # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by # fully-qualified names, including namespaces. If set to NO, the class list will # be sorted only by class name, not including the namespace part. # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. # Note: This option applies only to the class list, not to the alphabetical # list. # The default value is: NO. SORT_BY_SCOPE_NAME = YES # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper # type resolution of all parameters of a function it will reject a match between # the prototype and the implementation of a member function even if there is # only one candidate or it is obvious which candidate to choose by doing a # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still # accept a match between prototype and implementation in such cases. # The default value is: NO. STRICT_PROTO_MATCHING = NO # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo # list. This list is created by putting \todo commands in the documentation. # The default value is: YES. GENERATE_TODOLIST = YES # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test # list. This list is created by putting \test commands in the documentation. # The default value is: YES. GENERATE_TESTLIST = YES # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug # list. This list is created by putting \bug commands in the documentation. # The default value is: YES. GENERATE_BUGLIST = YES # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) # the deprecated list. This list is created by putting \deprecated commands in # the documentation. # The default value is: YES. GENERATE_DEPRECATEDLIST= YES # The ENABLED_SECTIONS tag can be used to enable conditional documentation # sections, marked by \if ... \endif and \cond # ... \endcond blocks. ENABLED_SECTIONS = # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the # initial value of a variable or macro / define can have for it to appear in the # documentation. If the initializer consists of more lines than specified here # it will be hidden. Use a value of 0 to hide initializers completely. The # appearance of the value of individual variables and macros / defines can be # controlled using \showinitializer or \hideinitializer command in the # documentation regardless of this setting. # Minimum value: 0, maximum value: 10000, default value: 30. MAX_INITIALIZER_LINES = 30 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at # the bottom of the documentation of classes and structs. If set to YES, the # list will mention the files that were used to generate the documentation. # The default value is: YES. SHOW_USED_FILES = NO # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This # will remove the Files entry from the Quick Index and from the Folder Tree View # (if specified). # The default value is: YES. SHOW_FILES = YES # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces # page. This will remove the Namespaces entry from the Quick Index and from the # Folder Tree View (if specified). # The default value is: YES. SHOW_NAMESPACES = YES # The FILE_VERSION_FILTER tag can be used to specify a program or script that # doxygen should invoke to get the current version for each file (typically from # the version control system). Doxygen will invoke the program by executing (via # popen()) the command command input-file, where command is the value of the # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided # by doxygen. Whatever the program writes to standard output is used as the file # version. For an example see the documentation. FILE_VERSION_FILTER = # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed # by doxygen. The layout file controls the global structure of the generated # output files in an output format independent way. To create the layout file # that represents doxygen's defaults, run doxygen with the -l option. You can # optionally specify a file name after the option, if omitted DoxygenLayout.xml # will be used as the name of the layout file. See also section "Changing the # layout of pages" for information. # # Note that if you run doxygen from a directory containing a file called # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE # tag is left empty. LAYOUT_FILE = @Range-v3_SOURCE_DIR@/doc/layout.xml # The CITE_BIB_FILES tag can be used to specify one or more bib files containing # the reference definitions. This must be a list of .bib files. The .bib # extension is automatically appended if omitted. This requires the bibtex tool # to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info. # For LaTeX the style of the bibliography can be controlled using # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the # search path. See also \cite for info how to create references. CITE_BIB_FILES = #--------------------------------------------------------------------------- # Configuration options related to warning and progress messages #--------------------------------------------------------------------------- # The QUIET tag can be used to turn on/off the messages that are generated to # standard output by doxygen. If QUIET is set to YES this implies that the # messages are off. # The default value is: NO. QUIET = NO # The WARNINGS tag can be used to turn on/off the warning messages that are # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES # this implies that the warnings are on. # # Tip: Turn warnings on while writing the documentation. # The default value is: YES. WARNINGS = YES # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag # will automatically be disabled. # The default value is: YES. WARN_IF_UNDOCUMENTED = NO # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for # potential errors in the documentation, such as documenting some parameters in # a documented function twice, or documenting parameters that don't exist or # using markup commands wrongly. # The default value is: YES. WARN_IF_DOC_ERROR = YES # If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete # function parameter documentation. If set to NO, doxygen will accept that some # parameters have no documentation without warning. # The default value is: YES. WARN_IF_INCOMPLETE_DOC = YES # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that # are documented, but have no documentation for their parameters or return # value. If set to NO, doxygen will only warn about wrong parameter # documentation, but not about the absence of documentation. If EXTRACT_ALL is # set to YES then this flag will automatically be disabled. See also # WARN_IF_INCOMPLETE_DOC # The default value is: NO. WARN_NO_PARAMDOC = NO # If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when # a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS # then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but # at the end of the doxygen process doxygen will return with a non-zero status. # Possible values are: NO, YES and FAIL_ON_WARNINGS. # The default value is: NO. WARN_AS_ERROR = NO # The WARN_FORMAT tag determines the format of the warning messages that doxygen # can produce. The string should contain the $file, $line, and $text tags, which # will be replaced by the file and line number from which the warning originated # and the warning text. Optionally the format may contain $version, which will # be replaced by the version of the file (if it could be obtained via # FILE_VERSION_FILTER) # See also: WARN_LINE_FORMAT # The default value is: $file:$line: $text. WARN_FORMAT = "$file:$line: $text" # In the $text part of the WARN_FORMAT command it is possible that a reference # to a more specific place is given. To make it easier to jump to this place # (outside of doxygen) the user can define a custom "cut" / "paste" string. # Example: # WARN_LINE_FORMAT = "'vi $file +$line'" # See also: WARN_FORMAT # The default value is: at line $line of file $file. WARN_LINE_FORMAT = "at line $line of file $file" # The WARN_LOGFILE tag can be used to specify a file to which warning and error # messages should be written. If left blank the output is written to standard # error (stderr). In case the file specified cannot be opened for writing the # warning and error messages are written to standard error. When as file - is # specified the warning and error messages are written to standard output # (stdout). WARN_LOGFILE = #--------------------------------------------------------------------------- # Configuration options related to the input files #--------------------------------------------------------------------------- # The INPUT tag is used to specify the files and/or directories that contain # documented source files. You may enter file names like myfile.cpp or # directories like /usr/src/myproject. Separate the files or directories with # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING # Note: If this tag is empty the current directory is searched. INPUT = @Range-v3_SOURCE_DIR@/include \ @Range-v3_SOURCE_DIR@/doc/index.md \ @Range-v3_SOURCE_DIR@/doc/examples.md \ @Range-v3_SOURCE_DIR@/doc/release_notes.md # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses # libiconv (or the iconv built into libc) for the transcoding. See the libiconv # documentation (see: # https://www.gnu.org/software/libiconv/) for the list of possible encodings. # The default value is: UTF-8. INPUT_ENCODING = UTF-8 # If the value of the INPUT tag contains directories, you can use the # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and # *.h) to filter out the source-files in the directories. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # read by doxygen. # # Note the list of default checked file patterns might differ from the list of # default file extension mappings. # # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp, # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, # *.hh, *.hxx, *.hpp, *.h++, *.l, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, # *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C # comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f18, *.f, *.for, *.vhd, # *.vhdl, *.ucf, *.qsf and *.ice. FILE_PATTERNS = *.hpp \ *.md # The RECURSIVE tag can be used to specify whether or not subdirectories should # be searched for input files as well. # The default value is: NO. RECURSIVE = YES # The EXCLUDE tag can be used to specify files and/or directories that should be # excluded from the INPUT source files. This way you can easily exclude a # subdirectory from a directory tree whose root is specified with the INPUT tag. # # Note that relative paths are relative to the directory from which doxygen is # run. EXCLUDE = @Range-v3_SOURCE_DIR@/include/range/v3/detail \ @Range-v3_SOURCE_DIR@/include/range/v3/algorithm/aux_ \ @Range-v3_SOURCE_DIR@/include/range/v3/algorithm/tagspec.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/at.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/back.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/begin_end.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/data.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/distance.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/empty.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/front.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/getlines.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/index.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/istream_range.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/iterator_range.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/range_access.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/range_concepts.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/range_traits.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/size.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/span.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/to_container.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/to_container.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/associated_types.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/basic_iterator.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/common_iterator.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/concepts.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/counted_iterator.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/dangling.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/functional.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/infinity.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/invoke.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/iterator_concepts.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/iterator_traits.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/iterator.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/nullptr_v.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/semiregular.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/tagged_pair.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/tagged_tuple.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/unreachable.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/utility/view_adaptor.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/view_adaptor.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/view_facade.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/view_interface.hpp \ @Range-v3_SOURCE_DIR@/include/range/v3/view/bounded.hpp # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or # directories that are symbolic links (a Unix file system feature) are excluded # from the input. # The default value is: NO. EXCLUDE_SYMLINKS = NO # If the value of the INPUT tag contains directories, you can use the # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude # certain files from those directories. # # Note that the wildcards are matched against the file with absolute path, so to # exclude all test directories for example use the pattern */test/* EXCLUDE_PATTERNS = # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names # (namespaces, classes, functions, etc.) that should be excluded from the # output. The symbol name can be a fully qualified name, a word, or if the # wildcard * is used, a substring. Examples: ANamespace, AClass, # ANamespace::AClass, ANamespace::*Test # # Note that the wildcards are matched against the file with absolute path, so to # exclude all test directories use the pattern */test/* EXCLUDE_SYMBOLS = # The EXAMPLE_PATH tag can be used to specify one or more files or directories # that contain example code fragments that are included (see the \include # command). EXAMPLE_PATH = @Range-v3_SOURCE_DIR@/example \ @Range-v3_SOURCE_DIR@/test # If the value of the EXAMPLE_PATH tag contains directories, you can use the # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and # *.h) to filter out the source-files in the directories. If left blank all # files are included. EXAMPLE_PATTERNS = * # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be # searched for input files to be used with the \include or \dontinclude commands # irrespective of the value of the RECURSIVE tag. # The default value is: NO. EXAMPLE_RECURSIVE = YES # The IMAGE_PATH tag can be used to specify one or more files or directories # that contain images that are to be included in the documentation (see the # \image command). IMAGE_PATH = @Range-v3_BINARY_DIR@/image # The INPUT_FILTER tag can be used to specify a program that doxygen should # invoke to filter for each input file. Doxygen will invoke the filter program # by executing (via popen()) the command: # # # # where is the value of the INPUT_FILTER tag, and is the # name of an input file. Doxygen will then use the output that the filter # program writes to standard output. If FILTER_PATTERNS is specified, this tag # will be ignored. # # Note that the filter must not add or remove lines; it is applied before the # code is scanned, but not when the output code is generated. If lines are added # or removed, the anchors will not be placed correctly. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # properly processed by doxygen. INPUT_FILTER = # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern # basis. Doxygen will compare the file name with each pattern and apply the # filter if there is a match. The filters are a list of the form: pattern=filter # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how # filters are used. If the FILTER_PATTERNS tag is empty or if none of the # patterns match the file name, INPUT_FILTER is applied. # # Note that for custom extensions or not directly supported extensions you also # need to set EXTENSION_MAPPING for the extension otherwise the files are not # properly processed by doxygen. FILTER_PATTERNS = # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using # INPUT_FILTER) will also be used to filter the input files that are used for # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). # The default value is: NO. FILTER_SOURCE_FILES = NO # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and # it is also possible to disable source filtering for a specific pattern using # *.ext= (so without naming a filter). # This tag requires that the tag FILTER_SOURCE_FILES is set to YES. FILTER_SOURCE_PATTERNS = # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that # is part of the input, its contents will be placed on the main page # (index.html). This can be useful if you have a project on for instance GitHub # and want to reuse the introduction page also for the doxygen output. USE_MDFILE_AS_MAINPAGE = #--------------------------------------------------------------------------- # Configuration options related to source browsing #--------------------------------------------------------------------------- # If the SOURCE_BROWSER tag is set to YES then a list of source files will be # generated. Documented entities will be cross-referenced with these sources. # # Note: To get rid of all source code in the generated output, make sure that # also VERBATIM_HEADERS is set to NO. # The default value is: NO. SOURCE_BROWSER = NO # Setting the INLINE_SOURCES tag to YES will include the body of functions, # classes and enums directly into the documentation. # The default value is: NO. INLINE_SOURCES = NO # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any # special comment blocks from generated source code fragments. Normal C, C++ and # Fortran comments will always remain visible. # The default value is: YES. STRIP_CODE_COMMENTS = YES # If the REFERENCED_BY_RELATION tag is set to YES then for each documented # entity all documented functions referencing it will be listed. # The default value is: NO. REFERENCED_BY_RELATION = YES # If the REFERENCES_RELATION tag is set to YES then for each documented function # all documented entities called/used by that function will be listed. # The default value is: NO. REFERENCES_RELATION = YES # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set # to YES then the hyperlinks from functions in REFERENCES_RELATION and # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will # link to the documentation. # The default value is: YES. REFERENCES_LINK_SOURCE = YES # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the # source code will show a tooltip with additional information such as prototype, # brief description and links to the definition and documentation. Since this # will make the HTML file larger and loading of large files a bit slower, you # can opt to disable this feature. # The default value is: YES. # This tag requires that the tag SOURCE_BROWSER is set to YES. SOURCE_TOOLTIPS = YES # If the USE_HTAGS tag is set to YES then the references to source code will # point to the HTML generated by the htags(1) tool instead of doxygen built-in # source browser. The htags tool is part of GNU's global source tagging system # (see https://www.gnu.org/software/global/global.html). You will need version # 4.8.6 or higher. # # To use it do the following: # - Install the latest version of global # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file # - Make sure the INPUT points to the root of the source tree # - Run doxygen as normal # # Doxygen will invoke htags (and that will in turn invoke gtags), so these # tools must be available from the command line (i.e. in the search path). # # The result: instead of the source browser generated by doxygen, the links to # source code will now point to the output of htags. # The default value is: NO. # This tag requires that the tag SOURCE_BROWSER is set to YES. USE_HTAGS = NO # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a # verbatim copy of the header file for each class for which an include is # specified. Set to NO to disable this. # See also: Section \class. # The default value is: YES. VERBATIM_HEADERS = NO # If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the # clang parser (see: # http://clang.llvm.org/) for more accurate parsing at the cost of reduced # performance. This can be particularly helpful with template rich C++ code for # which doxygen's built-in parser lacks the necessary type information. # Note: The availability of this option depends on whether or not doxygen was # generated with the -Duse_libclang=ON option for CMake. # The default value is: NO. CLANG_ASSISTED_PARSING = NO # If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS # tag is set to YES then doxygen will add the directory of each input to the # include path. # The default value is: YES. # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. CLANG_ADD_INC_PATHS = YES # If clang assisted parsing is enabled you can provide the compiler with command # line options that you would normally use when invoking the compiler. Note that # the include paths will already be set by doxygen for the files and directories # specified with INPUT and INCLUDE_PATH. # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. CLANG_OPTIONS = # If clang assisted parsing is enabled you can provide the clang parser with the # path to the directory containing a file called compile_commands.json. This # file is the compilation database (see: # http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the # options used when the source files were built. This is equivalent to # specifying the -p option to a clang tool, such as clang-check. These options # will then be passed to the parser. Any options specified with CLANG_OPTIONS # will be added as well. # Note: The availability of this option depends on whether or not doxygen was # generated with the -Duse_libclang=ON option for CMake. CLANG_DATABASE_PATH = #--------------------------------------------------------------------------- # Configuration options related to the alphabetical class index #--------------------------------------------------------------------------- # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all # compounds will be generated. Enable this if the project contains a lot of # classes, structs, unions or interfaces. # The default value is: YES. ALPHABETICAL_INDEX = NO # In case all classes in a project start with a common prefix, all classes will # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag # can be used to specify a prefix (or a list of prefixes) that should be ignored # while generating the index headers. # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. IGNORE_PREFIX = #--------------------------------------------------------------------------- # Configuration options related to the HTML output #--------------------------------------------------------------------------- # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output # The default value is: YES. GENERATE_HTML = YES # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of # it. # The default directory is: html. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_OUTPUT = html # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each # generated HTML page (for example: .htm, .php, .asp). # The default value is: .html. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FILE_EXTENSION = .html # The HTML_HEADER tag can be used to specify a user-defined HTML header file for # each generated HTML page. If the tag is left blank doxygen will generate a # standard header. # # To get valid HTML the header file that includes any scripts and style sheets # that doxygen needs, which is dependent on the configuration options used (e.g. # the setting GENERATE_TREEVIEW). It is highly recommended to start with a # default header using # doxygen -w html new_header.html new_footer.html new_stylesheet.css # YourConfigFile # and then modify the file new_header.html. See also section "Doxygen usage" # for information on how to generate the default header that doxygen normally # uses. # Note: The header is subject to change so you typically have to regenerate the # default header when upgrading to a newer version of doxygen. For a description # of the possible markers and block names see the documentation. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_HEADER = # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each # generated HTML page. If the tag is left blank doxygen will generate a standard # footer. See HTML_HEADER for more information on how to generate a default # footer and what special commands can be used inside the footer. See also # section "Doxygen usage" for information on how to generate the default footer # that doxygen normally uses. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FOOTER = # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style # sheet that is used by each HTML page. It can be used to fine-tune the look of # the HTML output. If left blank doxygen will generate a default style sheet. # See also section "Doxygen usage" for information on how to generate the style # sheet that doxygen normally uses. # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as # it is more robust and this tag (HTML_STYLESHEET) will in the future become # obsolete. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_STYLESHEET = # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined # cascading style sheets that are included after the standard style sheets # created by doxygen. Using this option one can overrule certain style aspects. # This is preferred over using HTML_STYLESHEET since it does not replace the # standard style sheet and is therefore more robust against future updates. # Doxygen will copy the style sheet files to the output directory. # Note: The order of the extra style sheet files is of importance (e.g. the last # style sheet in the list overrules the setting of the previous ones in the # list). For an example see the documentation. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_EXTRA_STYLESHEET = # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or # other source files which should be copied to the HTML output directory. Note # that these files will be copied to the base HTML output directory. Use the # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these # files. In the HTML_STYLESHEET file, use the file name only. Also note that the # files will be copied as-is; there are no commands or markers available. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_EXTRA_FILES = # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen # will adjust the colors in the style sheet and background images according to # this color. Hue is specified as an angle on a color-wheel, see # https://en.wikipedia.org/wiki/Hue for more information. For instance the value # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 # purple, and 360 is red again. # Minimum value: 0, maximum value: 359, default value: 220. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_HUE = 75 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors # in the HTML output. For a value of 0 the output will use gray-scales only. A # value of 255 will produce the most vivid colors. # Minimum value: 0, maximum value: 255, default value: 100. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_SAT = 100 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the # luminance component of the colors in the HTML output. Values below 100 # gradually make the output lighter, whereas values above 100 make the output # darker. The value divided by 100 is the actual gamma applied, so 80 represents # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not # change the gamma. # Minimum value: 40, maximum value: 240, default value: 80. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_COLORSTYLE_GAMMA = 80 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML # page will contain the date and time when the page was generated. Setting this # to YES can help to show when doxygen was last run and thus if the # documentation is up to date. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_TIMESTAMP = NO # If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML # documentation will contain a main index with vertical navigation menus that # are dynamically created via JavaScript. If disabled, the navigation index will # consists of multiple levels of tabs that are statically embedded in every HTML # page. Disable this option to support browsers that do not have JavaScript, # like the Qt help browser. # The default value is: YES. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_DYNAMIC_MENUS = YES # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the # page has loaded. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_DYNAMIC_SECTIONS = YES # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries # shown in the various tree structured indices initially; the user can expand # and collapse entries dynamically later on. Doxygen will expand the tree to # such a level that at most the specified number of entries are visible (unless # a fully collapsed tree already exceeds this amount). So setting the number of # entries 1 will produce a full collapsed tree by default. 0 is a special value # representing an infinite number of entries and will result in a full expanded # tree by default. # Minimum value: 0, maximum value: 9999, default value: 100. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_INDEX_NUM_ENTRIES = 0 # If the GENERATE_DOCSET tag is set to YES, additional index files will be # generated that can be used as input for Apple's Xcode 3 integrated development # environment (see: # https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To # create a documentation set, doxygen will generate a Makefile in the HTML # output directory. Running make will produce the docset in that directory and # running make install will install the docset in # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at # startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy # genXcode/_index.html for more information. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_DOCSET = NO # This tag determines the name of the docset feed. A documentation feed provides # an umbrella under which multiple documentation sets from a single provider # (such as a company or product suite) can be grouped. # The default value is: Doxygen generated docs. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_FEEDNAME = "Doxygen generated docs" # This tag determines the URL of the docset feed. A documentation feed provides # an umbrella under which multiple documentation sets from a single provider # (such as a company or product suite) can be grouped. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_FEEDURL = # This tag specifies a string that should uniquely identify the documentation # set bundle. This should be a reverse domain-name style string, e.g. # com.mycompany.MyDocSet. Doxygen will append .docset to the name. # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_BUNDLE_ID = org.doxygen.Project # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify # the documentation publisher. This should be a reverse domain-name style # string, e.g. com.mycompany.MyDocSet.documentation. # The default value is: org.doxygen.Publisher. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_ID = org.doxygen.Publisher # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. # The default value is: Publisher. # This tag requires that the tag GENERATE_DOCSET is set to YES. DOCSET_PUBLISHER_NAME = Publisher # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three # additional HTML index files: index.hhp, index.hhc, and index.hhk. The # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop # on Windows. In the beginning of 2021 Microsoft took the original page, with # a.o. the download links, offline the HTML help workshop was already many years # in maintenance mode). You can download the HTML help workshop from the web # archives at Installation executable (see: # http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo # ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe). # # The HTML Help Workshop contains a compiler that can convert all HTML output # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML # files are now used as the Windows 98 help format, and will replace the old # Windows help format (.hlp) on all Windows platforms in the future. Compressed # HTML files also contain an index, a table of contents, and you can search for # words in the documentation. The HTML workshop also contains a viewer for # compressed HTML files. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_HTMLHELP = NO # The CHM_FILE tag can be used to specify the file name of the resulting .chm # file. You can add a path in front of the file if the result should not be # written to the html output directory. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. CHM_FILE = # The HHC_LOCATION tag can be used to specify the location (absolute path # including file name) of the HTML help compiler (hhc.exe). If non-empty, # doxygen will try to run the HTML help compiler on the generated index.hhp. # The file has to be specified with full path. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. HHC_LOCATION = # The GENERATE_CHI flag controls if a separate .chi index file is generated # (YES) or that it should be included in the main .chm file (NO). # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. GENERATE_CHI = NO # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) # and project file content. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. CHM_INDEX_ENCODING = # The BINARY_TOC flag controls whether a binary table of contents is generated # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it # enables the Previous and Next buttons. # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. BINARY_TOC = NO # The TOC_EXPAND flag can be set to YES to add extra items for group members to # the table of contents of the HTML help documentation and to the tree view. # The default value is: NO. # This tag requires that the tag GENERATE_HTMLHELP is set to YES. TOC_EXPAND = NO # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help # (.qch) of the generated HTML documentation. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_QHP = NO # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify # the file name of the resulting .qch file. The path specified is relative to # the HTML output folder. # This tag requires that the tag GENERATE_QHP is set to YES. QCH_FILE = # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help # Project output. For more information please see Qt Help Project / Namespace # (see: # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace). # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_QHP is set to YES. QHP_NAMESPACE = org.doxygen.Project # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt # Help Project output. For more information please see Qt Help Project / Virtual # Folders (see: # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders). # The default value is: doc. # This tag requires that the tag GENERATE_QHP is set to YES. QHP_VIRTUAL_FOLDER = doc # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom # filter to add. For more information please see Qt Help Project / Custom # Filters (see: # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_CUST_FILTER_NAME = # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the # custom filter to add. For more information please see Qt Help Project / Custom # Filters (see: # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_CUST_FILTER_ATTRS = # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this # project's filter section matches. Qt Help Project / Filter Attributes (see: # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_SECT_FILTER_ATTRS = # The QHG_LOCATION tag can be used to specify the location (absolute path # including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to # run qhelpgenerator on the generated .qhp file. # This tag requires that the tag GENERATE_QHP is set to YES. QHG_LOCATION = # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be # generated, together with the HTML files, they form an Eclipse help plugin. To # install this plugin and make it available under the help contents menu in # Eclipse, the contents of the directory containing the HTML and XML files needs # to be copied into the plugins directory of eclipse. The name of the directory # within the plugins directory should be the same as the ECLIPSE_DOC_ID value. # After copying Eclipse needs to be restarted before the help appears. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_ECLIPSEHELP = NO # A unique identifier for the Eclipse help plugin. When installing the plugin # the directory name containing the HTML and XML files should also have this # name. Each documentation set should have its own identifier. # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. ECLIPSE_DOC_ID = org.doxygen.Project # If you want full control over the layout of the generated HTML pages it might # be necessary to disable the index and replace it with your own. The # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top # of each HTML page. A value of NO enables the index and the value YES disables # it. Since the tabs in the index contain the same information as the navigation # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. DISABLE_INDEX = YES # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index # structure should be generated to display hierarchical information. If the tag # value is set to YES, a side panel will be generated containing a tree-like # index structure (just like the one that is generated for HTML Help). For this # to work a browser that supports JavaScript, DHTML, CSS and frames is required # (i.e. any modern browser). Windows users are probably better off using the # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can # further fine tune the look of the index (see "Fine-tuning the output"). As an # example, the default style sheet generated by doxygen has an example that # shows how to put an image at the root of the tree instead of the PROJECT_NAME. # Since the tree basically has the same information as the tab index, you could # consider setting DISABLE_INDEX to YES when enabling this option. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. GENERATE_TREEVIEW = YES # When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the # FULL_SIDEBAR option determines if the side bar is limited to only the treeview # area (value NO) or if it should extend to the full height of the window (value # YES). Setting this to YES gives a layout similar to # https://docs.readthedocs.io with more room for contents, but less room for the # project logo, title, and description. If either GENERATE_TREEVIEW or # DISABLE_INDEX is set to NO, this option has no effect. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. FULL_SIDEBAR = NO # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that # doxygen will group on one line in the generated HTML documentation. # # Note that a value of 0 will completely suppress the enum values from appearing # in the overview section. # Minimum value: 0, maximum value: 20, default value: 4. # This tag requires that the tag GENERATE_HTML is set to YES. ENUM_VALUES_PER_LINE = 4 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used # to set the initial width (in pixels) of the frame in which the tree is shown. # Minimum value: 0, maximum value: 1500, default value: 250. # This tag requires that the tag GENERATE_HTML is set to YES. TREEVIEW_WIDTH = 270 # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to # external symbols imported via tag files in a separate window. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. EXT_LINKS_IN_WINDOW = NO # If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email # addresses. # The default value is: YES. # This tag requires that the tag GENERATE_HTML is set to YES. OBFUSCATE_EMAILS = YES # If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg # tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see # https://inkscape.org) to generate formulas as SVG images instead of PNGs for # the HTML output. These images will generally look nicer at scaled resolutions. # Possible values are: png (the default) and svg (looks nicer but requires the # pdf2svg or inkscape tool). # The default value is: png. # This tag requires that the tag GENERATE_HTML is set to YES. HTML_FORMULA_FORMAT = png # Use this tag to change the font size of LaTeX formulas included as images in # the HTML documentation. When you change the font size after a successful # doxygen run you need to manually remove any form_*.png images from the HTML # output directory to force them to be regenerated. # Minimum value: 8, maximum value: 50, default value: 10. # This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_FONTSIZE = 10 # Use the FORMULA_TRANSPARENT tag to determine whether or not the images # generated for formulas are transparent PNGs. Transparent PNGs are not # supported properly for IE 6.0, but are supported on all modern browsers. # # Note that when changing this option you need to delete any form_*.png files in # the HTML output directory before the changes have effect. # The default value is: YES. # This tag requires that the tag GENERATE_HTML is set to YES. FORMULA_TRANSPARENT = YES # The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands # to create new LaTeX commands to be used in formulas as building blocks. See # the section "Including formulas" for details. FORMULA_MACROFILE = # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see # https://www.mathjax.org) which uses client side JavaScript for the rendering # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX # installed or if you want to formulas look prettier in the HTML output. When # enabled you may also need to install MathJax separately and configure the path # to it using the MATHJAX_RELPATH option. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. USE_MATHJAX = NO # With MATHJAX_VERSION it is possible to specify the MathJax version to be used. # Note that the different versions of MathJax have different requirements with # regards to the different settings, so it is possible that also other MathJax # settings have to be changed when switching between the different MathJax # versions. # Possible values are: MathJax_2 and MathJax_3. # The default value is: MathJax_2. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_VERSION = MathJax_2 # When MathJax is enabled you can set the default output format to be used for # the MathJax output. For more details about the output format see MathJax # version 2 (see: # http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3 # (see: # http://docs.mathjax.org/en/latest/web/components/output.html). # Possible values are: HTML-CSS (which is slower, but has the best # compatibility. This is the name for Mathjax version 2, for MathJax version 3 # this will be translated into chtml), NativeMML (i.e. MathML. Only supported # for NathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This # is the name for Mathjax version 3, for MathJax version 2 this will be # translated into HTML-CSS) and SVG. # The default value is: HTML-CSS. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_FORMAT = HTML-CSS # When MathJax is enabled you need to specify the location relative to the HTML # output directory using the MATHJAX_RELPATH option. The destination directory # should contain the MathJax.js script. For instance, if the mathjax directory # is located at the same level as the HTML output directory, then # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax # Content Delivery Network so you can quickly see the result without installing # MathJax. However, it is strongly recommended to install a local copy of # MathJax from https://www.mathjax.org before deployment. The default value is: # - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2 # - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3 # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax # extension names that should be enabled during MathJax rendering. For example # for MathJax version 2 (see https://docs.mathjax.org/en/v2.7-latest/tex.html # #tex-and-latex-extensions): # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols # For example for MathJax version 3 (see # http://docs.mathjax.org/en/latest/input/tex/extensions/index.html): # MATHJAX_EXTENSIONS = ams # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_EXTENSIONS = # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces # of code that will be used on startup of the MathJax code. See the MathJax site # (see: # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an # example see the documentation. # This tag requires that the tag USE_MATHJAX is set to YES. MATHJAX_CODEFILE = # When the SEARCHENGINE tag is enabled doxygen will generate a search box for # the HTML output. The underlying search engine uses javascript and DHTML and # should work on any modern browser. Note that when using HTML help # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) # there is already a search function so this one should typically be disabled. # For large projects the javascript based search engine can be slow, then # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to # search using the keyboard; to jump to the search box use + S # (what the is depends on the OS and browser, but it is typically # , /