- Boost - lists.preview.boost.org

[uBlas] [Tensor] multiprecision and FFT?
by Janek Kozicki 07 Jan '21

07 Jan '21

Cem Bassoy via Boost said: (by the date of Wed, 6 Jan 2021 10:32:15 +0100) > Please consider to use and contribute to *Boost.uBlas* Hi, Does it work with boost::multiprecision types? In particular I am interested in types listed here: http://yade-dem.org/doc/HighPrecisionReal.html Does it support FFT ? In particular I am interested in replacing my very crude NDimTable class with your code: https://gitlab.com/cosurgi/trunk/-/blob/addQuantumMechanics_FixEnum_FixReba… I am about to start refactoring this part of the code, when I noticed your post. best regards Janek -- Janek Kozicki, PhD. DSc. Arch. Assoc. Prof. Gdańsk University of Technology Faculty of Applied Physics and Mathematics Department of Theoretical Physics and Quantum Information -- http://yade-dem.org/ http://pg.edu.pl/jkozicki (click English flag on top right)

2 3

C++11 on up Boost libraries
by Edward Diener 04 Jan '21

04 Jan '21

In my effort to set the meta information of 'cxxstd' for the appropriate C++11 on up libraries, my PRs for these libraries have been kindly merged to 'develop' by the library maintainers: beast callable_traits context convert coroutine2 fiber geometry gil hana histogram hof json leaf mp11 nowide outcome pfr process safe_numerics static_string stl_interfaces variant2 yap If anyone knows of any other current library which is a C++11 on up library, please tell me. My testing showed that all other Boost libraries will work in C++03 mode, but maybe I missed some other library which is a C++11 on up library. Needless to say other libraries have noted their attention to move from C++03 to C++11 in the near future. If any library does change the C++ mode necessary to use that library, I hope the maintainer(s) of that library will update the 'cxxstd' meta information appropriately. If we can get the website to work properly using the 'cxxstd' meta information, end-users should be able to know immediately whether a Boost library is usable depending on the C++ standard mode their are using.

10 20

Develop is broken on MSVC (b2 issue?)
by Antony Polukhin 04 Jan '21

04 Jan '21

I see a bunch of CI failures https://apolukhin.github.io/en/developer.html for different versions of MSVC. There are some complains on 'cl': compile-c-c++ ..\..\..\bin.v2\libs\type_index\test\track_13621.test\msvc-9.0\release\threading-multi\track_13621.obj 'cl' is not recognized as an internal or external command, operable program or batch file. call "..\..\..\bin.v2\standalone\msvc\msvc-9.0\msvc-setup.bat" amd64 >nul cl /Zm800 -nologo "track_13621.cpp" -Fo"..\..\..\bin.v2\libs\type_index\test\track_13621.test\msvc-9.0\release\threading-multi\track_13621.obj" -TP -DBOOST_TRAVISCI_BUILD /wd4675 /EHs /GR /O2 /Ob2 /W3 /MD /Zc:forScope /Zc:wchar_t /favor:blend -c -DBOOST_ALL_NO_LIB=1 -DNDEBUG "-I..\..\.." ...failed compile-c-c++ ..\..\..\bin.v2\libs\type_index\test\track_13621.test\msvc-9.0\release\threading-multi\track_13621.obj... Is that a known issue?

3 3

Regression Test Failures On develop branch
by Tom Kent 02 Jan '21

02 Jan '21

I just noticed that the develop branch has started to fail to run the develop branch, crashing early on in the run. The failures started sometime between 2020-12-31_03:52:29 PST (2020-12-31_11:52:29 UTC) (last good run) and 2020-12-31_06:57:54 PST (2020-12-31_14:57:54 UTC) (first failing run). These are still continuing with the latest develop branch. It looks like there were only a couple commits to boostorg/boost/develop in this window, and update to multiprecision (only changing meta/libraries.json) and a few changes to build. The error looks fairly non-descript... D:\teeks99-09\run\boost_root\status>"D:\teeks99-09\run\boost_bb\src\engine\bjam.exe" "-sBOOST_BUILD_PATH=D:\teeks99-09\run;D:\teeks99-09\run\boost_bb\src" "-sBOOST_ROOT=D:\teeks99-09\run\boost_root" "--boost=D:\teeks99-09\run\boost_root" "--boost-root=D:\teeks99-09\run\boost_root" "--boost-build=D:\teeks99-09\run\boost_bb\src" "--debug-configuration" -l300 toolset=msvc-11.0 -d2 preserve-test-targets=off --dump-tests -j8 address-model=64 --remove-test-targets --abbreviate-paths debug-symbols=off -m64 "--build-dir=D:\teeks99-09\run\results" 1>>"D:\teeks99-09\run\results\bjam.log" 2>&1 # Running Boost.Build tests Traceback (most recent call last): File "run.py", line 71, in <module> runner(root) File "D:\teeks99-09\run\boost_regression_src\regression.py", line 286, in __init__ self.main() File "D:\teeks99-09\run\boost_regression_src\regression.py", line 623, in main getattr(self,action_m)() File "D:\teeks99-09\run\boost_regression_src\regression.py", line 588, in command_regression self.command_test() File "D:\teeks99-09\run\boost_regression_src\regression.py", line 367, in command_test self.command_test_boost_build() File "D:\teeks99-09\run\boost_regression_src\regression.py", line 409, in command_test_boost_build "boost/bin.v2/libs/any/test/any_test.test")); WindowsError: [Error 3] The system cannot find the path specified: 'D:\\teeks99-09\\run\\results\\boost/bin.v2/libs/any/test/any_test.test\\*.*' At the end of my result-bjam.log file, I get this, but not sure if it is related. Performing configuration checks - default architecture : x86 - default address-model : 64-bit - symlinks supported : no - junctions supported : yes - hardlinks supported : yes - BOOST_COMP_GNUC >= 4.3.0 : no - has_icu builds : no - compiler supports SSE2 : yes - compiler supports SSE4.1 : yes - has synchronization.lib : yes - cxx11_constexpr : no - cxx11_decltype : yes - cxx11_hdr_tuple : no - cxx11_template_aliases : no - cxx11_variadic_templates : no - OpenCL : no - C++11 mutex : yes - has BCrypt API : yes - has stat::st_mtim : no - has stat::st_mtimensec : no - has stat::st_mtimespec : no - has stat::st_birthtim : no - has stat::st_birthtimensec : no - has stat::st_birthtimespec : no - has statx : no - has statx syscall : no - cxx11_auto_declarations : yes - cxx11_defaulted_functions : no - cxx11_final : yes - cxx11_hdr_mutex : yes - cxx11_lambdas : yes - cxx11_noexcept : no - cxx11_nullptr : yes - cxx11_rvalue_references : yes - cxx11_thread_local : no - cxx11_trailing_result_types : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam. note: to suppress this message, pass "--without-graph_parallel" to bjam. - cxx14_constexpr : no - cxx14_decltype_auto : no - cxx14_generic_lambdas : no - cxx14_return_type_deduction : no - cxx11_user_defined_literals : no - cxx11_alignas : no - iconv (libc) : no - iconv (separate) : no - icu : no - icu (lib64) : no - native atomic int32 supported : yes - has message compiler : yes - native syslog supported : no - pthread supports robust mutexes : no - compiler supports SSSE3 : yes - compiler supports AVX2 : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - cxx11_static_assert : yes - std::fstream is moveable and swappable : yes - !BOOST_COMP_GNUC : yes - BOOST_COMP_GNUC >= 6.0 : no - !BOOST_COMP_CLANG : yes - BOOST_COMP_CLANG >= 4.0 : no - cxx14_variable_templates : no - BOOST_COMP_GNUC >= 4.7.4 : no error: No best alternative for ../libs/accumulators/test/accumulators_test_valarray next alternative: required properties: <link>static <target-os>linux <toolset>clang not matched next alternative: required properties: <link>static <target-os>darwin not matched next alternative: required properties: <link>static not matched error: No best alternative for ../libs/accumulators/test/accumulators_test_tail_variate_means next alternative: required properties: <link>static <toolset-msvc:version>14.0 <toolset>msvc not matched next alternative: required properties: <link>static not matched error: No best alternative for ../libs/accumulators/test/accumulators_tests_pot_quantile_and_weighted_tail next alternative: required properties: <link>static <target-os>linux <toolset-gcc:version>4.4.7 <toolset>gcc not matched next alternative: required properties: <link>static not matched error: No best alternative for ../libs/accumulators/test/accumulators_test_weighted_tail_variate_means next alternative: required properties: <link>static <target-os>linux <toolset-gcc:version>4.4.7 <toolset>gcc not matched next alternative: required properties: <link>static <toolset-msvc:version>14.0 <toolset>msvc not matched next alternative: required properties: <link>static not matched - cxx11_constexpr : no - cxx11_decltype : yes - cxx11_hdr_tuple : no - cxx11_template_aliases : no - cxx11_variadic_templates : no - OpenCL : no - has_atomic_lib builds : no - has_pthread_lib builds : no - has_rt_lib builds : no - Clang implicit fallthrough : no - int128 : no - cpp_lib_complex_udls : no - cpp_range_based_for_17 : no - cxx11_hdr_thread : yes - cxx11_variadic_macros : yes - cxx11_hdr_unordered_set : yes - mixed_cxxstd builds : yes - mixed_cxxstd builds : yes - cxx11_hdr_array : yes - cxx11_defaulted_functions : no - cxx11_trailing_result_types : no notice: [libjpeg] Using pre-installed library notice: [libjpeg] Condition notice: [zlib] zlib is already configured notice: [libpng] Using pre-installed library notice: [libpng] Condition notice: [libtiff] Using pre-installed library notice: [libtiff] Condition - cxx14_constexpr : no - cxx14_decltype_auto : no - cxx14_generic_lambdas : no - cxx14_return_type_deduction : no - cxx11_user_defined_literals : no - Checking for gmpxx.h : no - zlib : no - bzip2 : no - lzma : no - zstd : no - lzma : no (cached) - has_lzma_cputhreads builds : no - cxx11_alignas : no - message-compiler : yes - message-compiler : yes - cxx11_unified_initialization_syntax : no - cxx11_smart_ptr : yes - GCC libquadmath and __float128 support : no - cxx11_hdr_initializer_list : no - sfinae_expr : no - cxx11_inline_namespaces : no - cxx11_range_based_for : yes - libfftw3 : no - __float128 : no - has_ntl_rr builds : no - has_mpfr_class builds : no - has_mpreal builds : no - has_e_float builds : no - gcc visibility : no - long double support : yes - cxx17_if_constexpr : no - cxx17_std_apply : no - has_eigen builds : no - Intel _Quad datatype support : no - has_mpfr builds : no - cxx11_hdr_atomic : no - cxx11_hdr_future : yes - cxx11_hdr_chrono : yes - cxx11_hdr_random : yes - cxx11_allocator : no - 128-bit floatmax_t : no - cxx11_numeric_limits : yes - cxx11_explicit_conversion_operators : no - cxx11_function_template_default_args : no - BOOST_MULTI_INDEX_KEY_SUPPORTED defined : no - has_gmp builds : no - has_tommath builds : no - has_mpfi builds : no - has_float128 builds : no - has_intel_quad builds : no - has_mpc builds : no - has_is_constant_evaluated builds : no - has_constexpr_limits builds : no - has_gmp builds : no - has_mpfr builds : no - has_big_obj builds : no - has_f2c builds : no - cxx11_noexcept : no - cxx11_rvalue_references : yes - cxx11_static_assert : yes - std::fstream is moveable and swappable : yes - cxx11_hdr_chrono : yes - !BOOST_COMP_GNUC : yes - BOOST_COMP_GNUC >= 6.0 : no - !BOOST_COMP_CLANG : yes - BOOST_COMP_CLANG >= 4.0 : no - cxx14_variable_templates : no - cxx17_structured_bindings : no - cxx17_structured_bindings : no - compiler_supports_loophole builds : yes - compiler_supports_loophole builds : yes - cxx11_hdr_unordered_map : yes WARNING: Unable to construct ../libs/predef/test/info_as_objcpp of type RUN with these properties: <abi>ms <address-model>64 <architecture>x86 <asynch-exceptions>off <bc_hdr>lib <bc_no>all_yes <binary-format>pe <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>off <deduced-address-model>64 <deduced-architecture>x86 <define>BOOST_ALL_NO_LIB=1 <define>BOOST_BEAST_ALLOW_DEPRECATED <define>BOOST_BEAST_SEPARATE_COMPILATION <dependency>object(file-target)@110440 <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <hardcode-dll-paths>true <host-os>windows <implicit-dependency>object(notfile-target)@92787 <include>.. <include>/D:/teeks99-09/run/boost_root/libs/predef/include <inlining>off <install-dependencies>off <link>shared <local-visibility>hidden <location-prefix>info_as_objcpp.test <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>off <profiling>off <python-debugging>off <python.interpreter>python <python>3.8 <relevant>define:<relevant>toolset <relevant>link:<relevant>toolset <relevant>python.interpreter:<relevant>python <relevant>python.interpreter:<relevant>target-os <relevant>threading:<relevant>runtime-link <relevant>threading:<relevant>toolset <relevant>toolset <response-file>auto <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <suppress-import-lib>false <symlink-location>project-relative <tag>@Jamfile<D:\teeks99-09\run\boost_root>%Jamfile<D:\teeks99-09\run\boost_root>.tag <target-os>windows <test-info>always_show_run_output <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>11.0 <toolset>msvc <user-interface>console <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <xsl:param>boost.defaults=Boost WARNING: Considered these as possible generators: WARNING: testing.expect-success with source types { RUN_OUTPUT } and requirements { } WARNING: Unable to construct ../libs/predef/test/info_as_objc of type RUN with these properties: <abi>ms <address-model>64 <architecture>x86 <asynch-exceptions>off <bc_hdr>lib <bc_no>all_yes <binary-format>pe <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>off <deduced-address-model>64 <deduced-architecture>x86 <define>BOOST_ALL_NO_LIB=1 <define>BOOST_BEAST_ALLOW_DEPRECATED <define>BOOST_BEAST_SEPARATE_COMPILATION <dependency>object(file-target)@110440 <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <hardcode-dll-paths>true <host-os>windows <implicit-dependency>object(notfile-target)@92787 <include>.. <include>/D:/teeks99-09/run/boost_root/libs/predef/include <inlining>off <install-dependencies>off <link>shared <local-visibility>hidden <location-prefix>info_as_objc.test <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>off <profiling>off <python-debugging>off <python.interpreter>python <python>3.8 <relevant>define:<relevant>toolset <relevant>link:<relevant>toolset <relevant>python.interpreter:<relevant>python <relevant>python.interpreter:<relevant>target-os <relevant>threading:<relevant>runtime-link <relevant>threading:<relevant>toolset <relevant>toolset <response-file>auto <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <suppress-import-lib>false <symlink-location>project-relative <tag>@Jamfile<D:\teeks99-09\run\boost_root>%Jamfile<D:\teeks99-09\run\boost_root>.tag <target-os>windows <test-info>always_show_run_output <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>11.0 <toolset>msvc <user-interface>console <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <xsl:param>boost.defaults=Boost WARNING: Considered these as possible generators: WARNING: testing.expect-success with source types { RUN_OUTPUT } and requirements { } - BOOST_OS_MACOS : no - BOOST_COMP_CLANG > 0.0.0 : no - BOOST_OS_LINUX == 0 : yes WARNING: Unable to construct ../libs/predef/test/info_as_objcpp of type RUN with these properties: <abi>ms <address-model>64 <architecture>x86 <asynch-exceptions>off <bc_hdr>lib <bc_no>all_yes <binary-format>pe <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>off <deduced-address-model>64 <deduced-architecture>x86 <define>BOOST_ALL_NO_LIB=1 <define>BOOST_BEAST_ALLOW_DEPRECATED <define>BOOST_BEAST_SEPARATE_COMPILATION <dependency>object(file-target)@110440 <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <hardcode-dll-paths>true <host-os>windows <implicit-dependency>object(notfile-target)@92787 <include>.. <include>/D:/teeks99-09/run/boost_root/libs/predef/include <inlining>off <install-dependencies>off <link>shared <local-visibility>hidden <location-prefix>info_as_objcpp.test <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>off <profiling>off <python-debugging>off <python.interpreter>python <python>3.8 <relevant>define:<relevant>toolset <relevant>link:<relevant>toolset <relevant>python.interpreter:<relevant>python <relevant>python.interpreter:<relevant>target-os <relevant>threading:<relevant>runtime-link <relevant>threading:<relevant>toolset <relevant>toolset <response-file>auto <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <suppress-import-lib>false <symlink-location>project-relative <tag>@Jamfile<D:\teeks99-09\run\boost_root>%Jamfile<D:\teeks99-09\run\boost_root>.tag <target-os>windows <test-info>always_show_run_output <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>11.0 <toolset>msvc <user-interface>console <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <xsl:param>boost.defaults=Boost WARNING: Considered these as possible generators: WARNING: testing.expect-success with source types { RUN_OUTPUT } and requirements { } WARNING: Unable to construct ../libs/predef/test/info_as_objc of type RUN with these properties: <abi>ms <address-model>64 <architecture>x86 <asynch-exceptions>off <bc_hdr>lib <bc_no>all_yes <binary-format>pe <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>off <deduced-address-model>64 <deduced-architecture>x86 <define>BOOST_ALL_NO_LIB=1 <define>BOOST_BEAST_ALLOW_DEPRECATED <define>BOOST_BEAST_SEPARATE_COMPILATION <dependency>object(file-target)@110440 <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <hardcode-dll-paths>true <host-os>windows <implicit-dependency>object(notfile-target)@92787 <include>.. <include>/D:/teeks99-09/run/boost_root/libs/predef/include <inlining>off <install-dependencies>off <link>shared <local-visibility>hidden <location-prefix>info_as_objc.test <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>off <profiling>off <python-debugging>off <python.interpreter>python <python>3.8 <relevant>define:<relevant>toolset <relevant>link:<relevant>toolset <relevant>python.interpreter:<relevant>python <relevant>python.interpreter:<relevant>target-os <relevant>threading:<relevant>runtime-link <relevant>threading:<relevant>toolset <relevant>toolset <response-file>auto <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <suppress-import-lib>false <symlink-location>project-relative <tag>@Jamfile<D:\teeks99-09\run\boost_root>%Jamfile<D:\teeks99-09\run\boost_root>.tag <target-os>windows <test-info>always_show_run_output <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>11.0 <toolset>msvc <user-interface>console <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <xsl:param>boost.defaults=Boost WARNING: Considered these as possible generators: WARNING: testing.expect-success with source types { RUN_OUTPUT } and requirements { } - zlib : no (cached) - bzip2 : no (cached) - lzma : no (cached) - zstd : no (cached) - zlib : no - bzip2 : no - lzma : no - zstd : no - auto_ptr : yes - cxx11_lambdas : yes - std_wstreambuf : yes - cxx11_hdr_forward_list : yes Happy new year! Tom

2 2

Re: [boost] Boost website changes and .'cxxstd`
by Donovan Dikaio 30 Dec '20

30 Dec '20

Hi Edward, you're right. The beta website link is https://beta.boost.org/ FYI, there is a file 'libraries.txt' in the source codes which contains all the libraries info. It looks like that it can be generated by a site tool. To my codes review, there exist multiple records for a library for various versions in the above text file. And the codes check and compare a library record’s version info with the current version, and pick one matching a condition. There is no record with 'cxxstd' field at the text file for beta website but for main site. Unfortunately, there is no one to match version comparison condition for main site as well at the moment. The updates codes of beta website will only show 'C++ standard minimum level' with 'cxxstd' value only if a 'cxxstd' value exists.

2 1

Potential order statistic tree?
by Soronel Haetir 29 Dec '20

29 Dec '20

Boost developers, Would there be interest in adding an order statistic tree to the boost library? That is, a tree that instead of being sorted simply keeps nodes in whatever order is specified, along with a (potentially multi-index) per-node value and a total of per-node values of each node and its left-descent tree. I currently have two such types, a very capable intrusive version (not based on boost::intrusive though using some of the same ideas) and a less capable non-intrusive form that uses the mechanics of the intrusive form as an implementation detail. The reason for not being based on Boost.Intrusive is that the tree algorithms that Boost.Intrusive provides are all for search trees and this very definitely is not, plus the need to alter node weights during insert, delete and rotations and the Boost.Intrusive algorithm providers not having a good place to add that behavior. I have personally found this type very useful while implementing a rope container and also while implementing tracking for various parts of a text editor (that is, paragraph, line and run positions) (in terms of characters, graphemes and screen height). Perhaps the major drawback to what I have is that I have not been careful to isolate c++-version dependent code. Although I know it does compile with the latest msvc 2019 as well as the clang 10.0 that MS ships. I am simply not sure whether such a type has a broad enough appeal to make the work of adding it to boost worthwhile. -- Soronel Haetir soronel.haetir(a)gmail.com

4 3

Boost website changes and .'cxxstd'
by Edward Diener 24 Dec '20

24 Dec '20

Even though I have worked a little with PHP in the past I do not have the talent to make the change to the website which would incorporate the addition of the meta information json field 'cxxstd' to the Boost documentation web page for each library. The idea is that if 'cxxstd' is set to a value the documentation for that library would also show: C++ standard minimum level: C++nn where nn would be 11, 14, 17, or 20 depending on the value of 'cxxstd'. Alternatively if there is no 'cxxstd' entry for a library or if the value of 'cxxstd' is '03', we could either specify 'nn' as '03' or leave off the line stating the 'C++ standard minimum level completely. On the face of it this should be doable in the website code but evidently Daniel James is the only one who really understands how this works in the code and he is no longer active in Boost. So if someone else who understands the website code and PHP could do this it would be appreciated, since I think it will be valuable telling end-users whether a Boost library is usable at the C++ compiler level they are using.

3 3

(no subject)
by Harsh 21 Dec '20

21 Dec '20

Respected Sir/Madam Myself Harsh Agarwal a highly interested candidate to work on with ublas as a open source contributor but at starting need some guidance-: 1-:How can i start on with it. 2-: As if i want to participate in Gsoc 2021 till when will i get competency test. 3-: can i know about the basic project idea that will be for gsoc 2021 thanking you Harsh Agarwal 21/12/2020

2 1

regarding boost gsoc competency test 2021
by Mohd Huzaifa 20 Dec '20

20 Dec '20

hii sir/madam I want to ask about the boost competency test for gsoc 2021. When it will be available. And can I get the list of past competency tests.

2 1

Tagging the minimum C++ standard level for Boost libs
by Edward Diener 19 Dec '20

19 Dec '20

I had previously proposed that we tag the minimum C++ standard level for Boost libs by adding information to the json meta information in libraries.json for each library. I would like to revisit that proposal, which involved more elaborate suggestions, with this simpler overall proposal: for each Boost C++ library whose minimum C++ standard level is C++11 or above we add a json field called 'cxxstd' whose value corresponds to one of the same values as currently exists in Boost.Build for the 'cxxstd' feature, ie. 11,14,17,20, to the libraries.json file for that library. This json value can then be used in Boost documentation of each library to specify the minimum C++ standard level needed by an end-user in order to use that library. Obviously we can also add "cxxstd": "03" for the many Boost libraries which can still be used at the C++98/C++03 compilation level also, even though I would argue that not having a "cxxstd" json field should mean C++98/C++03 by default. I would be willing to create the necessary PRs for each library, as I have a pretty good internal list of this information. The gist of this proposal is to make it much easier for end-users wishing to use a Boost library to immediately know whether the library they wish to use is usable at the C++ standard compilation level they are using for compilation, without having to spend time searching for such information, which is often not readily available, in the documentation of the library they are considering. I can go ahead and start doing this now, but of course I am willing to listen to what others think about this. But let's not let another round of inertia stop doing at all what should be a simple means of telling end-user's whether a Boost library is at least minimally usable by them in their C++ projects.

5 13