February 2019 - Boost - lists.preview.boost.org

CMake Announcement from Boost Steering Committee
by Jon Kalb 13 Aug '24

13 Aug '24

The libraries produced by the Boost community have had a greater impact on the way that the C++ community writes code than any other library implementation. The focus of the Boost community will always be on the libraries, but it is undeniable that we are dependent on and often limited by the infrastructure of our trade. Years ago, the move to Git was contentious; yet, it was required to improve development. In a similar vein our build system has become an impediment for many developers and users, existing and prospective. Therefore, we, the Steering Committee, announce to the Boost community our desire and intent to move Boost’s build system to CMake for users and developers alike. We are soliciting comments and proposals from the community to guide the process and the goals. Our desire is that the community can come to consensus by the end of the calendar year with a vision of supporting users and developers. We understand that the actual process of achieving the end goal will be long, time consuming, and not without its share of conflict. We also recognize that the Boost community is comprised of bright and passionate individuals that are eager to get involved and help get work done. The members of the Steering Committee have been encouraged by the discussions and activity surrounding CMake on the mailing lists over the years and know that many people have voiced visions. We hope that each of you rejoins the discussion to support this initiative and contributes to the common goal of improving Boost’s integration into the broader C++ ecosystem. For the Boost Steering Committee, Jon Kalb, Chair jonkalb(a)boost.org

49 199

[asio][coroutine] forbid_suspend blocks
by Vinícius dos Santos Oliveira 07 Aug '19

07 Aug '19

I've implemented a dumb linter using Python + clang API that allows you to mark certain blocks as “atomic in respect to coroutines” using C++11 attributes. Usage example follows: void f() { int yield; g(yield); [[bt::forbid_suspend]] { // Comment this call to make linter accept the code g(yield); t(); } } You can change bt::forbid_suspend to another identifier by tuning settings on the beginning of the script. The prefix forbid was inspired by Rust's linters[1] as you cannot disallow the linter from inside the forbid_suspend block. Some limitations follow: - A suspend point is identified by looking references to any id equals to yield in the last argument passed to function calls. It means that yield[ignored_ec] and alike will be correctly identified, but it needs to be named yield and it needs to be the last argument to the function call. - I haven't found a way to extract attributes related to COMPOUND_STMT nodes with clang API, so I manually look for token gaps and do a simple regex. It means you cannot use macros to [[bt::forbid_suspend]] as the macro won't be expanded. - You better call the script with '-x c++' and also ' -I/usr/lib/clang/5.0.1/include'. Like I've said in the beginning of the email, it's a *dumb* linter, which means it doesn't try to handle all cases. Therefore, I don't hope to do many changes to it or maintain it to work against newer releases of clang and I'm only uploading it to gist (not fullblow Github): < https://gist.github.com/vinipsmaker2/d930fbe5b7597432b021effe618da171>. It should also be easy to hack as it is very small. I'm releasing the linter under public domain. Enjoy. I have been using fibers in a daily basis on the last months of my job to solve networking problems on a gateway project. Some of the technologies I use are: - Boost.Asio and its spawn function. - A few custom synchronization primitives for the fibers (e.g. mutex, semaphore). - Eventually I'll have to write a custom spawn function that returns a joinable handle so I can kill the usage of a fiber::barrier in a few places. I've been using the linter for about a week already and looks fine. My use case are: - To prevent iterator invalidation in regions accessing shared variables. - To guarantee events order in algorithms that handle races (cannot yield while task YYY hasn't finished). The project I use it in is not an open source project, so I cannot talk much more about it. Also, I don't claim my solution is original. I wouldn't be surprised if the very same solution exists in the wild (please let me know if you know of a similar approach). This is not a new problem. It is know for some time. For instance, in P0171, Gor Nishanov noted this same problem: “In coroutines the suspend point is clearly marked with await, which tells the reader that something unusual happens in this function and allows the reader, for example, to confirm whether the lifetimes of the objects of interest align with the lifetime of the coroutine or not, whether some locks need to be acquired to protect some concurrently accessed data, and whether some locks need to be released before the execution reaches the suspend point.” — <http://open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0171r0.html>, 2015 However, the solution he presented was to manually examine whole blocks of code without help from the compiler. I argue that the solution he presented is as error-prone as manually looking for exit paths that don't free acquired resources in languages lacking RAII. And I've been spoiled too much by RAII. Furthermore, I take this comment of his with highly suspicious look: “Since we are on the subject of maintenance nightmares, we would like to offer a conjecture that the absence of the await in P0114 is a likely source of many maintenance nightmares. Without a syntactic marker to signal to the person reading the code that something funny is going on, it is impossible to tell whether the following code is correct or not” — http://open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0171r0.html If I had to give a vote to the proposal he was defending or Chris' proposal, I'd probably have chosen Chris'. [1] https://doc.rust-lang.org/reference/attributes.html# lint-check-attributes -- Vinícius dos Santos Oliveira https://vinipsmaker.github.io/

2 3

Non-ASCII Path Names in Repo
by Tom Kent 25 May '19

25 May '19

In the last few days we've had a non-ASCII path name added to the repo: tools/boostdep/test/utf8-test-ßµ™∃ Which came with commit 8893d1c57951a [1] I noticed this because a python 2 script (calling shutil.copytree) I had running on windows that copied the repo around started to fail. I've long needed to update that script to python 3, and am working on this. However, I wanted to point this out to the list so we could discuss if there are any other ramifications of having a non-ascii path. I vaguely remember some discussion about something like this in the past, but couldn't find it via search. If this is already a settled topic, that's great. Tom [1] https://github.com/boostorg/boostdep/commit/8893d1c57951a4a83705ed203005576…

2 1

Re: [boost] [ Interest? ] [ out_ptr ] Tiny C++ Abstraction for C-Style Output Pointers
by Bjorn Reese 12 May '19

12 May '19

On 06/28/18 21:03, ThePhD via Boost wrote: > out_ptr is a small abstraction for making types such as > std::unique_ptr, std::shared_ptr, boost::shared_ptr, and the upcoming > std::retain_ptr > <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0468r0.html> work > work C-Style output functions as a parameter, addressing the need of > wanting to be able to do "my_c_api_init( foo, bar, &my_smart_ptr );". It's Does out_ptr have other use-cases than C interoperability?

7 14

[thread] compiler error gcc 7.3 on cygwin
by James E. King III 06 May '19

06 May '19

Getting an internal compiler error with gcc 7.3 but only on cygwin 64-bit. Jim@pulsar /cygdrive/c/boost/libs/thread $ ../../b2 --abbreviate-paths toolset=gcc cxxstd=11 define=_POSIX_C_SOURCE=200112L define=__USE_ISOC99 threadapi=pthread address-model=64 variant=release -q ... gcc.compile.c++ ../../bin.v2/libs/thread/test/test_10963_c.test/gcc-7.3.0/rls/cxstd-11-iso/thrd-mlt/vsblt-hdn/test_10963_c.o In file included from ../../boost/thread/detail/invoker.hpp:30:0, from ../../boost/thread/future.hpp:31, from ../../libs/thread/test/test_10963.cpp:13: ../../boost/thread/detail/invoke.hpp: In function ‘decltype (*(forward<A0>)(boost::detail::invoke::a0).*boost::detail::invoke::f) boost::detail::invoke(Fp&&, A0&&) [with Fp = void (boost::executors::basic_thread_pool::*)(); A0 = boost::executors::basic_thread_pool*]’: ../../boost/thread/detail/invoke.hpp:102:43: internal compiler error: in gimplify_expr, at gimplify.c:12006 return (*boost::forward<A0>(a0)).*f; ^ Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. "g++" -std=c++11 -fvisibility-inlines-hidden -m64 -mthreads -O3 -finline-functions -Wno-inline -Wall -pedantic -fvisibility=hidden -Wextra -Wno-long-long -Wno-unused-parameter -Wunused-function -pedantic -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_THROW_IF_PRECONDITION_NOT_SATISFIED -DNDEBUG -D_POSIX_C_SOURCE=200112L -D__USE_ISOC99 -I"../.." -c -o "../../bin.v2/libs/thread/test/test_10963_c.test/gcc-7.3.0/rls/cxstd-11-iso/thrd-mlt/vsblt-hdn/test_10963_c.o" "../../libs/thread/test/test_10963.cpp" ...failed gcc.compile.c++ ../../bin.v2/libs/thread/test/test_10963_c.test/gcc-7.3.0/rls/cxstd-11-iso/thrd-mlt/vsblt-hdn/test_10963_c.o... If I change the C++ language level to 03 the problem goes away. I also cannot reproduce it on linux with the same version of compiler (but it probably isn't the exact same compiler code). Should I go ahead and file that gcc bug? - Jim

2 1

Building Boost 1.69 with Visual Studio 1.69
by Trueman, Chris 26 Mar '19

26 Mar '19

Maybe I'm getting ahead of myself given the recent topic about picking a version number for the latest MSVC toolset but I'm having trouble building boost 1.69 with Visual Studio 2019 preview. I blindly assumed the toolset was 14.20 (given the directory where cl.exe is found). Letting b2 determine the version yields vc141 in the lib names. Trying to force 142 with: using msvc : 14.2 : <path to cl.exe> ; in project-config.jam yields errors about unescaped characters. Suggestions welcomed. Chris. INTELLICORP LEGAL NOTICE: This E-Mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you received this message in error, please notify the sender immediately by replying to this message, and then delete it.

6 11

[test] unit test command-line handling
by Stefan Seefeld 22 Mar '19

22 Mar '19

Hello, this is a question concerning the Boost.Test framework. I'd like to pass command-line arguments to my tests, and I'm unsure of how to proceed. I have found https://www.boost.org/doc/libs/1_68_0/libs/test/doc/html/boost_test/adv_sce…, which shows how to access the command-line programmatically, but that's declared obsolete, and it's also lacking some important info, such as how I should handle the argv vector. Are there any examples that demonstrate this use case ? Specifically: * What (non-deprecated) API can I use to access command-line arguments during test initialization ? * How does my own handling of command-line arguments interact with Boost.Test's own command-line argument handling ? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

3 8

[release] 1.70.0 closed for major changes
by Marshall Clow 07 Mar '19

07 Mar '19

The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week. Also, if you're ready, you can also add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.q… > After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change. As always, the calendar for the release cycle is available at: https://www.boost.org/development/ Thanks, -- The Boost Release Team

7 9

[variant2] Need rationale for never-empty guarantee
by Andrzej Krzemienski 04 Mar '19

04 Mar '19

Hi Peter, Thank you for writing and sharing this implementation of variant. I am sorry if I am bringing back an issue that has been already discussed and solved before, but I do not understand the rationale behind doing compromises in order to provide the never-empty guarantee. The short rationale provided in Boost.Variant library: https://www.boost.org/doc/libs/1_69_0/doc/html/variant/design.html#variant.… was provided before we got C++11 the moved-from state in the language. Today, it should come as no surprise to programmers that a type might be in a "moved from" state where only a limited interface of an object can be used. The guarantee provided by variant's assignment is not a strong exception safety guarantee: it is possible that my variant has value A, I want to assign value B, and (due to an exception) I end up with value C. If this happens, the only thing I can reasonably do is to either abandon whatever I was doing or reset the variant to the state that I need. So the guarantee that it is not left empty does not seem to be of much use. But the cost to be paid is noticeable. I think that this question should be addressed in the documentation. Regards, Andrzej

13 51

GSoC 2019
by Shourya IIT B 04 Mar '19

04 Mar '19

Respected Sir, I am Parashuram Shourya from India. Currently, I am doing my Master’s in Geoinformatics from Centre of Studies in Resources Engineering(CSRE), Indian Institute of Technology Bombay(IITB). I have a Bachelor's degree in Computer Science and Engineering. Currently, I am learning Machine Learning and High-Performance Computing. I have vast programming experience in C, C++, Python I would love to contribute to The Qt Project in the upcoming Google Summer of Code 2019. I would be very grateful to get any directions to start with so that I can pursue and participate in GSoC 2019 with your organization.

2 1

GSoC 2019: we're in again!
by David Bellot 04 Mar '19

04 Mar '19

Dear Boost community, this year again, Boost C++ has been accepted as a mentor organization for the Google Summer of Code 2019. We are very happy to be part of this program every year because it brings talented students and a substantial amount of money to our organization to support our work toward the best libraries in C++. If you want to be a mentor, please propose your project now here: https://github.com/boostorg/boost/wiki/Google-Summer-of-Code:-2019 It's very important to write your proposal as soon as possible to attract the best students. If you have any questions, please contact me immediately. If you happen to be in Sydney, come and have a chat with me directly. Happy coding, David

3 3

Regarding project idea for GSOC 2019
by Syed Souban 04 Mar '19

04 Mar '19

Hi guys! I am a machine learning enthusiast looking forward to work in implementing some machine learning algorithms in c++ as a gsoc 2019 project. I know that a similar project has been done last year. So in a way I want to extend to that idea. I needed some suggestions and or pointers on which algorithms are feasible to implement. Regards, Souban

2 1

[Boost.Intrusive]
by PREET THAKKAR 03 Mar '19

03 Mar '19

I am a 2nd year computer science student. I want to contribute to Boost.Intrusive as part of GSoC '19. I have some ideas to enhance Boost.Intrusive and also add more features to previous year's project in Intrusive. I am new to Boost. Any help regarding getting started with the library would be appreciated. Regards, Preet Thakkar

2 1

Re: [boost] Review request for variant2, review manager wanted
by Peter Dimov 03 Mar '19

03 Mar '19

> If anyone would like to step forward to manage the review, please do. Michael Caisse was the first to graciously offer his services (via Slack) and I'll be glad to have him manage the review. Thanks to Niall who also volunteered. :-) With respect to Niall's request for compile time and run time measurements, I've added a benchmark https://github.com/pdimov/variant2/blob/develop/benchmark/benchmark1.cpp and the results from compiling and running it on my machine are at https://github.com/pdimov/variant2/blob/develop/benchmark/benchmark1.md This is not a cherry-picked example that makes variant2 look good, so it loses to std::variant here and there. :-)

7 13

Re: [boost] [Boost-testing] Running regression tests for msvc-14.2 (preview)
by Tom Kent 02 Mar '19

02 Mar '19

On Tue, Feb 26, 2019 at 7:13 AM Mateusz Loskot via Boost-Testing < boost-testing(a)lists.boost.org> wrote: > On Tue, 26 Feb 2019 at 14:02, Tom Kent via Boost-Testing > <boost-testing(a)lists.boost.org> wrote: > > I was hoping to start running regression tests for the upcoming Visual > Studio 2019 (toolset 14.2) and got stumped by an issue. > > I've set a user-config.jam: > > using msvc : 14.2 ; > > Is this toolset even supported? > > As I explained in > https://lists.boost.org/Archives/boost/2019/02/245143.php, > I had to 'fake' it as 14.1 in project-config.jam: > > using msvc : 14.1 : "C:\\Program Files (x86)\\Microsoft Visual > > Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.20.27323\\bin\\HostX64\\x64\\cl.exe" > I was able to get the regression tests to run using this workaround in user-config.jam. Here's what the config_info is: https://www.boost.org/development/tests/develop/developer/output/teeks99-te… I'm disappointed that we can't have general support for future versions of msvc. We don't seem to have this problem with pre-release versions of GCC/Clang. https://www.boost.org/development/tests/develop/developer/output/teeks99-02… Tom

3 5

Review request for variant2, review manager wanted
by Peter Dimov 28 Feb '19

28 Feb '19

I'd like to request a formal Boost review for the Variant2 library, https://github.com/pdimov/variant2. Variant2 contains an implementation of a variant<T...> type that is an almost conforming std::variant, except it doesn't require C++17 and supports C++11 and above. It's also never valueless and has a few other extensions. The same library also contains an expected<T, E...> type, which is like the proposed std::expected<T, E>, but supports more than one error type. expected<> is not yet production-ready and has no test suite, but I will finish it if the library is accepted. The documentation for the variant<T...> class is at https://pdimov.github.io/variant2/index.html. If anyone would like to step forward to manage the review, please do.

10 15

Contributing to Boost.Algorithm
by Juho Lauri 28 Feb '19

28 Feb '19

Hello all, I'd be interested in contributing towards Boost.Algorithm - what's the appropriate way forward? Or perhaps this question has already been asked somewhere and I'd appreciate if you could point me to the right place. Thanks

1 0

A Unicode library?
by Can Topal 28 Feb '19

28 Feb '19

Hello everyone, Since I regularly work with Unicode text, I have started to design a Unicode library for handling UTF 8,16 and 32. The current support in C++ is still limited. Mainly I'm trying to implement a STL like support for file reading/writing, I/O operations and memory storage. So a user could read/write and process Unicode text like an ASCII string without knowing how the text is encoded. I thought people might have use for it. Even though libraries like ICU exist, they aren't beginner friendly and I couldn't find one with decent support for I/O. Is there demand for this? And if so do you guys have any suggestions? Thank you. - Onur

4 3

[GSOC19] [GIL]Image processing algorithms
by Shardul Parab 27 Feb '19

27 Feb '19

Hi! I am Shardul Parab, a computer science student from the Birla Institute of Technology and Science, Pilani. I am highly interested in contributing to Boost via GSoC 2019 and would love to contribute to the GIL library(as per the project idea listed). I believe that I have good practical experience of image processing techniques and if given the opportunity would be a great learning opportunity too. I have a decent experience with the library and would like to ask as to whether there is any particular task that I could begin with for the project and begin contributing from now itself under the guidance of a mentor. Thanking you, Regards. Shardul Parab

2 1

[GSOC2019][uBLAS] Linear and Multilinear Algebra with Matrix and Tensor Computations
by Ashar 27 Feb '19

27 Feb '19

Hi, I am Ashar Khan, a Second Year Computer Science Student from India. I would like to work with boost for Summer of Code 2019 and improve on the existing *boost.uBLAS *library. I have completed the Programming Competency test of uBLAS and find myself perfect for the task. I am looking forward to a mentor who can help me in the later parts of the project. I request any Potential mentor of uBLAS (David Bellot, Stefan Seefeld, and Sem Bassoy) to help me start my work. You can check my programming test on the following link here <https://github.com/coder3101/gsoc19-boost-test> Any Suggestions and opinions on the test are welcomed. Sorry if I did wrong by open-sourcing my test. I did not find any specific instructions as to how to submit the test. Looking forward to hearing from you soon. Thanks and Regards Ashar

2 1

Help regarding GSoC '19
by VIVEK MODI 27 Feb '19

27 Feb '19

Hey, I hope I am in the right mailing list. I am Vivek here. I am interested in working in the project Boost generic image library (project 1) listed by mentor Stefan Seefeld. If anyone can guide how to proceed further regarding the programming competency test and contributing to the project it would be of great help. -- Regards - Vivek Modi BTech(Information Technology) NIT Durgapur INDIA

2 1

[gsoc2019][astronomy] Program competency test
by rittik verma 27 Feb '19

27 Feb '19

Hello, I was reading through the competency test for boost astronomy and was struck by a question, should each coordinate has its own unit, for example, x - length, y - time, z-force? or just one unit for all coordinates? Thank you

2 1

clang-win clang-cl.exe on Windows 10 - is it time to add clang-win to the Boost test matrix?
by Paul A. Bristow 27 Feb '19

27 Feb '19

Confirming the work of others (pdimov and degski et al), I am now getting good results using clang-win (Clang 8.0.0 rc using GCC provided by Mingw64) on Windows 10. (Clang 8.0.0 should be finally released very soon now). Working the develop branch (fully up-to-date), I can run the Boost.Math examples and tests, and build the a set of most libraries (4 versions of most, for example) 27-Feb-19 14:32 15,872 boost_atomic-clangw8-mt-d-x64-1_70.dll 27-Feb-19 14:32 2,442 boost_atomic-clangw8-mt-d-x64-1_70.lib 27-Feb-19 14:32 9,728 boost_atomic-clangw8-mt-x64-1_70.dll 27-Feb-19 14:32 2,420 boost_atomic-clangw8-mt-x64-1_70.lib (but there are some failures to compile or to link). Examples in Addendum below: My user-config.jam contains using clang-win : # Clang Version. 8.0.0 : # Location of Clang compiler .exe file(s). Must use clang-cl driver, not clang++.exe # Copied path is "C:\LLVM\clang-700\LLVM\bin\clang-cl.exe" "C:/LLVM/clang-800/LLVM/bin/clang-cl.exe" -fuse-ld=lld # Use lld linker https://lld.llvm.org/, not clang++. # : # Options. <cxxflags>-v # Verbose output for testing only. ? --verbose does not work for clang? # <define>BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE # <compileflags>-m64 Use address-model=64 on command line. <compatibility>vc14 # MS version compatibility. <cxxflags>-fmsc-version=1915 <cxxflags>-fms-compatibility <cxxflags>-fno-delayed-template-parsing #https://clang.llvm.org/docs/CommandGuide/clang.html#cmdoption-s # options are -flto, -flto=full, -flto=thin, -emit-llvm # Generate output files in LLVM formats, suitable for link time optimization. # The default for -flto is "full", in which the LLVM bitcode is suitable for monolithic Link Time Optimization (LTO), # where the linker merges all such modules into a single combined module for optimization. # With "thin", ThinLTO compilation is invoked instead. <cxxflags>-flto=thin # MS clang-cl compatibility settings: <cxxflags>"/std:c++17" # Must be c++17, not earlier. <cxxflags>"/Zc:forScope" <cxxflags>"/Zc:wchar_t" <cxxflags>"/EHsc" # exception handling # https://docs.microsoft.com/en-us/cpp/build/reference/eh-exception-handling-… # (/EHsc), catches C++ exceptions only and tells the compiler to assume that # functions declared as extern "C" never throw a C++ exception. <cxxflags>"/Zc:inline" <cxxflags>"/Gd" <cxxflags>"/diagnostics:classic" # Clang flags: # https://clang.llvm.org/docs/ClangCommandLineReference.html#compilation-flags # <cxxflags>-std=c++17 - already declared as a MS option. <cxxflags>-Wno-deprecated <cxxflags>-Wno-delete-non-virtual-dtor # <cxxflags>-fmacro-backtrace-limit=0 # <cxxflags>-Wno-invalid-token-paste <cxxflags>-Wno-language-extension-token <cxxflags>-Wno-microsoft-enum-value <cxxflags>-Wno-literal-range <cxxflags>-Wno-unknown-pragmas <cxxflags>-Wno-unused-variable <cxxflags>-Wno-microsoft-enum-value # <cxxflags>-Wno-invalid-constexpr # Need to stop reporting an error in Boost.System? <cxxflags>-Wno-unknown-argument <cxxflags>-Wno-unknown-pragmas <cxxflags>-Wno-macro-redefined <cxxflags>-Wno-unused-variable <cxxflags>-Wno-mismatched-tags <cxxflags>-Wno-deprecated-declarations <define>_CRT_SECURE_NO_DEPRECATE <define>_CRT_SECURE_NO_WARNINGS # Not all these may be needed to get a mostly warning-free build. ... My build command is \modular-boost>b2 -j4 toolset=clang-win-8.0.0 address-model=64 architecture=x86 --libdir=I:/modular-boost/lib --build-type=complete --without=mpi --without=python install 1>../boost_clang-win-8.0.0_64_config_27-Feb-19_1507.log I wonder if this means that it is time to add clang-win-8 configuration to the Boost Test summary at https://www.boost.org/development/tests/develop/developer/summary.html ? Paul PS What I have failed to get working is __float128 which works using GCC, but even after a patch enabling Clang in multiprecision's config and ensuring that quadmath.h is visible to the Clang compiler. It reports "not supported" :-( I have enquired if any progress can be made on making this work. Addendum - problem examples: ======================== LLVM ERROR: Associative COMDAT symbol '??_7codecvt_error_cat@?A0x15DB13AB@@6B@' does not exist. lld-link: error: undefined symbol: __imp_CryptGenRandom >>> referenced by I:\modular-boost\libs\random\src\random_device.cpp:121 >>> lto.tmp:("public: unsigned int __cdecl boost::random::random_device::impl::next(void)" (?next@impl@random_device@random@boost@@QEAAIXZ)) clang-cl: error: linker command failed with exit code 1 (use -v to see invocation) "C:/LLVM/clang-800/LLVM/bin/clang-cl.exe" "-fuse-ld=lld" -m64 /link /incremental:no /DLL /DEBUG /subsystem:console /out:"bin.v2\libs\random\build\clang-win-8.0.0\debug\address-model-64\threading-multi\boost_random-clangw8-mt-d-x64-1_70.dll" /IMPLIB:"bin.v2\libs\random\build\clang-win-8.0.0\debug\address-model-64\threading-multi\boost_random-clangw8-mt-d-x64-1_70.lib" @"bin.v2\libs\random\build\clang-win-8.0.0\debug\address-model-64\threading-multi\boost_random-clangw8-mt-d-x64-1_70.dll.rsp" if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL% and most annoyingly, since Boost.Test is a key library, "I:\modular-boost\lib\boost_unit_test_framework-clangw8-mt-d-x64-1_70.dll" "I:\modular-boost\lib\boost_unit_test_framework-clangw8-mt-d-x64-1_70.lib" but no release variants :-( clang-win.link.dll bin.v2\libs\test\build\clang-win-8.0.0\release\address-model-64\threading-multi\boost_unit_test_framework-clangw8-mt-x64-1_70.dll LLVM ERROR: Associative COMDAT symbol '??_7results_reporter_impl@?A0x22C2280D@results_reporter@unit_test@boost@@6B@' does not exist. clang-cl: error: linker command failed with exit code 1 (use -v to see invocation) "C:/LLVM/clang-800/LLVM/bin/clang-cl.exe" "-fuse-ld=lld" -m64 /link /incremental:no /DLL /subsystem:console /out:"bin.v2\libs\test\build\clang-win-8.0.0\release\address-model-64\threading-multi\boost_unit_test_framework-clangw8-mt-x64-1_70. dll" /IMPLIB:"bin.v2\libs\test\build\clang-win-8.0.0\release\address-model-64\threading-multi\boost_unit_test_framework-clangw8-mt-x64-1_ 70.lib" @"bin.v2\libs\test\build\clang-win-8.0.0\release\address-model-64\threading-multi\boost_unit_test_framework-clangw8-mt-x64-1_70.dll. rsp" if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL% ...failed clang-win.link.dll bin.v2\libs\test\build\clang-win-8.0.0\release\address-model-64\threading-multi\boost_unit_test_framework-clangw8-mt-x64-1_70.dll bin.v2\libs\test\build\clang-win-8.0.0\release\address-model-64\threading-multi\boost_unit_test_framework-clangw8-mt-x64-1_70.lib... --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

1 0

Running regression tests for msvc-14.2 (preview)
by Tom Kent 27 Feb '19

27 Feb '19

I was hoping to start running regression tests for the upcoming Visual Studio 2019 (toolset 14.2) and got stumped by an issue. I've set a user-config.jam: using msvc : 14.2 ; using python : 2.7 # version : C:\\Python27-32\\python.exe # Interperter/path to dir : C:\\Python27-32\\include # includes : C:\\Python27-32\\libs # libs : <address-model>32 <address-model> # conditions ; using python : 2.7 # version : C:\\Python27-64\\python.exe # Interperter/path to dir : C:\\Python27-64\\include # includes : C:\\Python27-64\\libs # libs : <address-model>64 # conditions ; Then I ran the command, from a vs2019 developer command prompt: D:\tmp>C:\Python27-64\python.exe run.py --runner=teeks99-test02 --toolsets=msvc-14.2 --tag=develop The full build output (minus some repetitive git and mklink commands) can be found here: https://gist.github.com/teeks99/2d72382bf13569855dbdcd2e0850c1cf A couple notable parts... Bootstrap says it is using the vc7 toolset, which isn't installed D:\tmp\boost_bb\src\engine>build.bat could not find "vswhere" ### ### Using 'vc7' toolset. ### but succeeds anyway, probably because cl.exe is available in the path in the vs2019 command prompt. B2.exe is successfully created and seems to work. During... notice: [python-cfg] Configuring python... [snip] ImportError: No module named numpy but that is normal. Finally, at the end...the real issue: ...skipped <p..\..\bin\testing\build\msvc-14.2\release\threading-multi>process_jam_log.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <p..\..\bin\common\build\msvc-14.2\release\threading-multi>process_jam_log.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... common.mkdir D:\tmp\boost_root\bin.v2 if not exist "D:\tmp\boost_root\bin.v2\\" mkdir "D:\tmp\boost_root\bin.v2" common.mkdir D:\tmp\boost_root\bin.v2\libs if not exist "D:\tmp\boost_root\bin.v2\libs\\" mkdir "D:\tmp\boost_root\bin.v2\libs" common.mkdir D:\tmp\boost_root\bin.v2\libs\filesystem if not exist "D:\tmp\boost_root\bin.v2\libs\filesystem\\" mkdir "D:\tmp\boost_root\bin.v2\libs\filesystem" common.mkdir D:\tmp\boost_root\bin.v2\libs\filesystem\build if not exist "D:\tmp\boost_root\bin.v2\libs\filesystem\build\\" mkdir "D:\tmp\boost_root\bin.v2\libs\filesystem\build" common.mkdir D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2 if not exist "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\\" mkdir "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2" common.mkdir D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release if not exist "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\\" mkdir "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release" common.mkdir D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static if not exist "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\\" mkdir "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static" common.mkdir D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi if not exist "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi\\" mkdir "D:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi" ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>codecvt_error_category.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>operations.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>path.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>path_traits.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>portability.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>unique_path.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>utf8_codecvt_facet.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>windows_file_codecvt.obj for lack of <p..\..\bin\standalone\msvc\msvc-14.2>msvc-setup.nup... ...skipped <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>libboost_filesystem-vc142-mt-1_70.lib for lack of <pD:\tmp\boost_root\bin.v2\libs\filesystem\build\msvc-14.2\release\link-static\threading-multi>codecvt_error_category.obj... ...skipped <p..\..\bin\testing\build\msvc-14.2\release\threading-multi>process_jam_log.exe for lack of <p..\..\bin\testing\build\msvc-14.2\release\threading-multi>process_jam_log.obj... ...skipped <pD:\tmp\boost_regression\stage\bin>process_jam_log.exe for lack of <p..\..\bin\testing\build\msvc-14.2\release\threading-multi>process_jam_log.exe... ...skipped 14 targets... ...updated 599 targets... # Searching for "process_jam_log.exe" in "D:\tmp\boost_regression\stage\bin"... Traceback (most recent call last): File "run.py", line 71, in <module> runner(root) File "D:\tmp\boost_regression_src\regression.py", line 286, in __init__ self.main() File "D:\tmp\boost_regression_src\regression.py", line 623, in main getattr(self,action_m)() File "D:\tmp\boost_regression_src\regression.py", line 580, in command_regression self.command_setup() File "D:\tmp\boost_regression_src\regression.py", line 351, in command_setup self.build_if_needed(self.process_jam_log,self.pjl_toolset) File "D:\tmp\boost_regression_src\regression.py", line 714, in build_if_needed tool[ 'build_path' ] = self.tool_path( tool ) File "D:\tmp\boost_regression_src\regression.py", line 739, in tool_path , '\n'.join( [ name_or_spec[ 'path' ], build_dir ] ) Exception: Cannot find "process_jam_log.exe" in any of the following locations: D:\tmp\boost_regression\stage\bin\process_jam_log.exe D:\tmp\boost_regression\stage\bin What is the msvc-setup.nup and where does it come from? Thanks, Tom

3 4

Building the Release Notes locally
by Vinnie Falco 27 Feb '19

27 Feb '19

Does anyone know how to build the release notes locally? I would like to know if they render correctly without going through an 8-hour Travis turnaround. The rumor mill says @Daniel James knows how to do it... Anyone?? Thanks

2 2

[Boost.astronomy]
by Viraj Sonaje 24 Feb '19

24 Feb '19

This is for the respective authority I am a 4th year engineering student. I want to contribute to Boost.astronomy library for GSOC 2019. I am familiar with the co-ordinate systems but I am new to boost.

2 1

Graph Algorithms
by Siddhartha Sen 24 Feb '19

24 Feb '19

Is there any interest in a library containing graph algorithms? Also, I am unable to find the list of maintainers of the respective libraries. Any information on that would be appreciated.

7 7

add serialization to circular_buffer
by Yuval Lifshitz 24 Feb '19

24 Feb '19

Dear Community,I have a PR [1] for supporting serialization of the circular_buffer. Main drive for this change, is my effort for adding serialization to boost accumulators [2] (some accumulators hold data internally in a circular buffer).The maintainers list [3] is not up to date regarding circular buffer, so, I'm not sure who the maintainer is (or if there is one). Would appreciate your help, so I can drive that to completion. Yuval Lifshitz [1] https://github.com/boostorg/circular_buffer/pull/25[2] https://github.com/boostorg/accumulators/pull/18 [3] https://github.com/boostorg/boost/blob/master/libs/maintainers.txt

1 0

BGL
by Siddhartha Sen 22 Feb '19

22 Feb '19

I looked up https://github.com/boostorg/boost/wiki/Google-Summer-of-Code:-2019 . No project ideas have been added for BGL as of yet, it seems. I hope there is something in BGL in this years GSOC, as I am really passionate about graphs and graph algorithms. Also, will you be mentoring this year? If not, do you have any information on the potential mentors for this BGL project? Thanks.

2 1

Re: [boost] Graph Algorithms
by Siddhartha Sen 22 Feb '19

22 Feb '19

Thanks for the feedback! But what if I focus on C++14 then? Is that a good idea? On Fri, 22 Feb, 2019, 6:14 PM Vinnie Falco, <vinnie.falco(a)gmail.com> wrote: > On Fri, Feb 22, 2019 at 12:49 AM Siddhartha Sen > <siddhartha99.sen(a)gmail.com> wrote: > > From what I've read in the mailing lists, I think the demand has > shifted > > from C++11 to more modern versions, like C++14 and C++17. Anyways, > > thanks for the tip. Will you be mentoring this year? > > I will not be mentoring directly although I do offer advice on the mailing > list. > > People say they want C++14 and C++17 but I don't think its a good idea > to require those language versions in a library, because most people > are still on C++11. Have a look at the latest developer survey: > > <https://www.jetbrains.com/research/devecosystem-2018/cpp/> > > If a library requires C++17 then most C++ users will not be able to > use it. And this is bad for the library, because fewer users means > less testing, less feedback, less popularity, and in general this > makes the library not as good. > > In terms of the API (interface) of a library, C++17 does not offer > much more than C++11 except for things like, avalability of > string_view, variant. But Boost has these things already (e.g. > boost::string_view, boost::variant) and they work in C++11. So there > is really no benefit to C++17 other than some improvements in the way > you can write the implementation. But that doesn't affect users > directly. > > In summary, by requiring C++17 most users will be unable to use the > code, and there will be very little benefit to C++17 users. > > Regards >

3 7

BGL
by Siddhartha Sen 22 Feb '19

22 Feb '19

I apologise. Actually, there was a suggestion in the boost mailing lists that there is a demand for this. Anyways, I am familiar with C++14 and a C++17 as well(a bit). Will you be mentoring this year? I have already read the documentation of LEMON and started using it as well. Please let me know what should I do next, or if there are any particular issues you would like me to work on. Thanks. Regards. Siddhartha.

2 1

BGL: Graph11
by Siddhartha Sen 22 Feb '19

22 Feb '19

Hi, I am SIddhartha Sen, a second year student in Information Science and Engineering. I hope to contribute to the BGL. I have heard that there is some interest in themodernization of BGL using modern C++11 concepts for improved performance. Being a GSOC 2019 aspirant, I was looking for a potential mentor in this domain to pair up with and get started on this project. Any help would be greatly appreciated. Thank You.

2 1

PR not merged
by Sreejith S 21 Feb '19

21 Feb '19

I have sent a PR[1]. Can I know why the PR is still not merged ? [1]:https://github.com/boostorg/graph/pull/158 -- Regards, Sreejith.S Amrita Vishwa Vidyapeetham FOSS@Amrita <http://amfoss.in> | Github <https://github.com/sreejithsankar55> | Blog <http://sreejithsankar.wordpress.com>

1 0

Re: [boost] [build] PROBLEM specifying libc++!!!!
by Nikita Kniazev 21 Feb '19

21 Feb '19

> Anyone know how to do this and have the will to make life easier for > poor overworked library maintainers? I have `b2 <stdlib>libc++` on CI for Spirit with https://github.com/boostorg/spirit/blob/develop/.travis.yml#L119-L121 When I tried to make a PR I stuck at the thing that I do not know how (or it is not possible) to format (free-)future value into some flags, i.e: > toolset.flags clang-linux.compile OPTIONS <stdlib> : -stdlib=[ value-of-feature <stdlib> ] ; > toolset.flags clang-linux.link OPTIONS <stdlib> : -stdlib=[ value-of-feature <stdlib> ] ; But since in the wild there are two possible options it might be ok to just hardcode them for now.

1 0

[GIL] Contribution to the library.
by Gaurav Hoskote 21 Feb '19

21 Feb '19

This is to inform the concerned authority that I am willing to participate in GSOC 2019 and wish to contribute to the GIL library. I am a final year student and have good understanding of operations like Thresholding, Morphology and various filters. I have an idea of how the library works and I wish to contribute to it under the guidance of a mentor.

2 1

Image Processing for [GIL] Boost.
by Gaurav Hoskote 21 Feb '19

21 Feb '19

The Boost GIL library lacks image processing header files for operations like thresholding, morphology etc. I intend to contribute to this library by proposing some header files that can be placed in this library. I have worked on image processing algorithms before and am familiar with all the concepts.I wish to work under the mentorship of Stefan Seefeld who posted this project on github for GSOC 2019. I have attached a proposal pdf file (gilpro.pdf) to this email which gives details about my work and how the project will be implemented along with goals and milestones to be achieved. Also, for competency test I have attached a sample header file (threshold.h) which gives a basic idea of what I wish to implement for my project. Feedback would be appreciated. Regards, Gaurav Hoskote.

1 0

[build] PROBLEM specifying libc++!!!!
by Vinnie Falco 21 Feb '19

21 Feb '19

This is hard to teach, hard to remember, and error prone: script: b2 -j3 libs/beast/test toolset=clang cxxstd=11 cxxflags=-stdlib=libc++ linkflags=-stdlib=libc++ There's an issue to address it in a straightforward fashion: <https://github.com/boostorg/build/issues/287> Anyone know how to do this and have the will to make life easier for poor overworked library maintainers? Regards

1 0

[GSoC 2019] cpp_int Improvement
by Fenil Mehta 20 Feb '19

20 Feb '19

Hi, Integers with the capability to store large numbers has always been a requirement in C++ which has successfully been implemented by boost/multiprecision/cpp_int. Other languages such as Python and Java also supports such integer datatypes. I performed a speed test for C++ and python integers. While comparing speed of cpp_int and python int, I noticed that even though C++ source program was compiled with -O2 and -O3 flags, cpp_int was slow as compared for python int for multiplication and left-shift operations. The time taken for multiplication was: 1) cpp_int = 17.06 seconds 2) python int = 8.39 seconds I used the attached files to perform the testing on Linux. The execution time was measured using the time command. I would like to optimize this library. Being a GSoC aspirant, I was looking to pair up with a potential mentor in this domain who could guide me. Any feedback would be appreciated. Regards, Fenil Mehta

2 1

[asio] windows compilation error
by Vinnie Falco 19 Feb '19

19 Feb '19

This program fails to compile under msvc.latest: #include <boost/asio.hpp> int main { return 0; } This program does compile: #define BOOST_ASIO_DISABLE_WINDOWS_RANDOM_ACCESS_HANDLE 1 #define BOOST_ASIO_DISABLE_WINDOWS_STREAM_HANDLE 1 #include <boost/asio.hpp> int main { return 0; } Thanks

1 0

Integer sorting
by Fenil Mehta 19 Feb '19

19 Feb '19

I have written a sorting algorithm which is way faster than std::sort for all array size. The link is as follows: https://github.com/fenilgmehta/Fastest-Integer-Sort Some guidance would be appreciated on how to improve the project structure and the steps to get it included in boost. Regards, Fenil Mehta

11 24

Regression tests broken
by Tom Kent 19 Feb '19

19 Feb '19

All- Sometime around 7pm yesterday (2-17) a commit went in (master and develop?, regression scripts?) that broke all my regression runners (linux and windows). I haven't had a ton of time to dig in, but the end of the results look like this: notice: using boost library auto_config <layout>system ../libs/contract/test/Jamfile.v2:417: Unescaped special character in argument <define>BOOST_CONTRACT_ON_MISSING_CHECK_DECL="{ throw err(); }" 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 /var/boost/run/boost_bb/src/build/feature.jam:447: in extend-feature from module feature error: coverage is already associated with the "<variant>" feature /var/boost/run/boost_bb/src/build/feature.jam:624: in feature.extend from module feature /var/boost/run/boost_bb/src/tools/features/variant-feature.jam:79: in variant from module variant-feature ../libs/histogram/Jamfile:15: in modules.load from module Jamfile</var/boost/run/boost_root/libs/histogram> /var/boost/run/boost_bb/src/build/project.jam:372: in load-jamfile from module project /var/boost/run/boost_bb/src/build/project.jam:64: in load from module project /var/boost/run/boost_bb/src/build/project.jam:109: in load-parent from module project /var/boost/run/boost_bb/src/build/project.jam:513: in initialize from module project /var/boost/run/boost_bb/src/build/project.jam:348: in load-jamfile from module project /var/boost/run/boost_bb/src/build/project.jam:64: in load from module project /var/boost/run/boost_bb/src/build/project.jam:142: in project.find from module project Jamfile.v2:122: in run-tests from module Jamfile</var/boost/run/boost_root/status> Jamfile.v2:196: in modules.load from module Jamfile</var/boost/run/boost_root/status> /var/boost/run/boost_bb/src/build/project.jam:372: in load-jamfile from module project /var/boost/run/boost_bb/src/build/project.jam:64: in load from module project /var/boost/run/boost_bb/src/build/project.jam:142: in project.find from module project /var/boost/run/boost_bb/src/build-system.jam:618: in load from module build-system /var/boost/run/boost_bb/src/kernel/modules.jam:295: in import from module modules /var/boost/run/boost_bb/src/kernel/bootstrap.jam:139: in boost-build from module /var/boost/run/boost_root/boost-build.jam:17: in module scope from module Any thoughts? Tom

6 6

[Asio][ssl] develop broken
by Damian Jarek 18 Feb '19

18 Feb '19

After the changes today (introduced in https://github.com/boostorg/asio/commit/0568d3bf0b492887c6c48d05f5492a782da… ) an overload of async_handshake( https://github.com/boostorg/asio/blob/develop/include/boost/asio/ssl/stream…) fails to compile because of the signature mismatch in async_result. This is a show-stopper, because it breaks quite a bit of code in Beast.

2 1

Searching and Sorting algorithms
by Siddhartha Sen 18 Feb '19

18 Feb '19

Sorry for the typo. I meant "generic", not genetic. Anyways, I went through the non-mutating algorithms section and can't think of anything to possibly add. I had three questions though: 1. Is there any interest in libraries aimed at solving any small but particular problem, for example, say tower of hanoi in minimum possible time? 2. For any existing algorithm, if we add some features would it be useful? For example, as far as I know, binary search returns true if an element is found and false, if not. What if we add the elements position if found? Does not change complexity, but makes it better to use,doesn't it? 3. I want to contribute to the sorting algorithms library as well, any idea where to start? Is there any scope for improvement of any existing algorithms? Also, if we want to add any entirely new algorithms of our own, any suggestions where to start? I am working on an algorithm currently and was hoping to propose it to the boost libraries. Sorry if my post got too lengthy. Any help would be appreciated. Thank You.

2 1

[Asio] develop broken on Windows
by Vinnie Falco 18 Feb '19

18 Feb '19

This program fails to compile on Windows: #include <boost/asio.hpp> int main() { return 0; } Regards

1 0

Searching Algorithm
by Siddhartha Sen 17 Feb '19

17 Feb '19

Looking to contribute to the sorting library under algorithms. Any mentors available? Also, is their any interest in searching algorithms? I looked up the boost libraries but couldn't find any. Are there any mentors available? I want to make a searching library which will be genetic in nature and applicable for all data types. Any guidance would be appreciated. Thanks. Siddhartha

2 1

building, debugging and contributing to an individual boost library
by Sean Farrow 17 Feb '19

17 Feb '19

Hi, Once I have forked an individual boost library, what is the best way of building the library with b2? How are dependencies on other libraries handled? Secondly, how can I build, run and debug tests using visual studio? Any help appreciated. Kind regards Sean.

6 7

New user need guidance.
by SHREYANS JAIN 17 Feb '19

17 Feb '19

Hi I am Shreyans Jain. I am new to opensource programming, can anyone guide me how to start contributing here. Thank You

1 0

Re: [boost] Mail list is poorly indexed by Google
by Nikita Kniazev 15 Feb '19

15 Feb '19

> > Indeed! Google stopped indexing January 2017. Strange, I linked mid-December thread, if crawlers stopped indexing in January there was more than two weeks to index it, is not it?

3 3

String Algorithms
by Siddhartha Sen 14 Feb '19

14 Feb '19

Hi, I would like to contribute to the string algorithms library for GSOC 2019. Are there any potential mentors to pair up with? I am also interested in algorithms in general, especially sorting and searching libraries. Is there any scope for contribution there as well? Any answers would be appreciated

1 0

Mail list is poorly indexed by Google
by Nikita Kniazev 13 Feb '19

13 Feb '19

I was going to find the https://lists.boost.org/Archives/boost/2018/12/244648.php thread, but it did not worked with Google (looked all the pages <https://www.google.com/search?q=dropping+support+for+msvc+9+site%3Alists.bo…>), while DuckDuckGo shows it as the first link <https://ddg.gg/?q=dropping+support+for+msvc+9+site%3Alists.boost.org>. Can webmasters look into this with the Google's Search Console <https://search.google.com/search-console/about>? Or it is a policy to supplant the all-embracing Google? :-)

2 1