- Boost - lists.boost.org

Re: [boost] Relevance of platfrom-specific shared_ptr implementations
by Bjorn Reese 31 May '20

31 May '20

On 2020-05-31 17:18, Peter Dimov via Boost wrote: > Those have been accumulated over the years and I'd like to clean them > up, remove the unused ones and fold as many of them as possible into a > few generic implementations using either std::atomic, GCC atomic > intrinsics > (https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/_005f_005fatomic-Builtins.html) > or GCC/intel sync intrinsics > (https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/_005f_005fsync-Builtins.html) How about a fall-back to Boost.Atomic?

1 0

Re: [boost] boost reviewLEAF Review of LEAF starts today : May 22 - May 31
by Jess 29 May '20

29 May '20

Hey, big boy! My boyfriend is visiting his parents for a week and I want to get laid. You actually live just nearby. Do you want to see some of my cheeky pictures? It is in my profile On this site | | | | Online Hookup | | | Kisses, Jess

3 2

[review][LEAF] Review period ending soon - May 31
by Michael Caisse 28 May '20

28 May '20

I'd like to encourage each of you to review Emil's error handling library. We often focus on design or implementation based reviews, and I encourage those but what I would really like to see are more user based reviews. Grab the library and docs and play with it a bit. What works well? What can be improved? As a reminder, some of LEAF's features include: * arbitrary error types * header-only * no dependencies * use without exceptions * use with exceptions * no dynamic memory alloc You can find the documentation here: <https://zajo.github.io/leaf/> and the library source here: <https://github.com/zajo/leaf/tree/review> Thanks! michael -- Michael Caisse Ciere Consulting ciere.com

1 0

[epochs] Proposal for an epoch-based organization of Boost libraries
by Joaquin M López Muñoz 28 May '20

28 May '20

Hi, Prompted by general feelings about Boost perceived lack of modernization and internal "bloat", and after an explicit survey on what users dislike about Boost [1], I decided to try and write a more or less fleshed out proposal for an epoch-based organization of Boost libraries. I've extensively tested and refined the proposal during discussions on Reddit and the Boost Slack channel, and I feel this is now ready for presentation at the mailing list: https://github.com/joaquintides/boost_epoch/blob/master/README.md I hope the proposal can start a productive conversation. Looking forward to your feedback. Best, Joaquín M López Muñoz [1]: https://www.reddit.com/r/cpp/comments/gfowpq/why_you_dont_use_boost/

13 42

Optional library
by anshu khare 27 May '20

27 May '20

Hi mentors I was going through the optional library of boost. I was facing some problem in understanding the code base. In lines from 94 to 97 in optional.hpp, the code is as follows: struct in_place_init_if_t { Struct init_tag{}; explicit in_place_init_if_t(init_tag) {} //not able to understand this line }; I understand that we are creating a structure in_place_init_if_t and inside that we are creating another structure init_tag and then we are calling the constructor of in_place_init_if_t. But I am not able to understand that what does it the constructor do when we pass init_tag as an argument to it. Is it same as we are creating a structure Car and then creating another structure wheels inside it and passing wheels as an argument to the constructor of car as follows: struct car { Struct wheels{}; explicit car(wheels) {} //not able to understand this line }; Could you please tell what is the significance of passing wheels as an argument in this counter example?

2 1

[LEAF] Loss of error_id
by Bjorn Reese 26 May '20

26 May '20

In the noexcept case, what happens in the Error-Handling function if the error_id generated by the Error-Reporting function is lost by the intermediate functions?

2 4

Request for 1.73 patch release
by Richard Hodges 25 May '20

25 May '20

Dear all, Just prior to the release of boost 1.73, some changes appeared in Asio which use the new c++20 concepts (and concepts-ts) features where available. These changes have introduced breakage in Beast in compilers where concepts are enabled. Examples are gcc=10 and clang10 with -std=c++20. I have pushed a fix to beast/develop to address this, but sadly we only became aware of the problem after the release of boost 1.73.0 I suspect the cause here is a combination of my relatively new appointment as a Beast maintainer and the ground-breaking event which I am sure c++20 will prove to be. I welcome any guidance on preparing or initiating a patch release as I lack the Arcane Knowledge required. For information, here is a link to the commit which fixes the problem: https://github.com/boostorg/beast/pull/1927 And some bug reports that alerted us that somethig was wrong: https://github.com/boostorg/beast/issues/1916 https://github.com/boostorg/beast/issues/1925 -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

6 13

Re: [boost] [LEAF] The usage of TLS
by Bjorn Reese 22 May '20

22 May '20

On 2020-05-04 01:15, Andrzej Krzemienski via Boost wrote: > There is a number of reasons people do not want to or cannot use the C++ > exception handling mechanism. One of them is that the implementation of > exception handling requires the usage of TLS, and TLS is not implementable > on some platforms, like GPUs. If Nvidia's compiler does not implement C++ > exception handling mechanism, it is not because it would be slow, but > because it would require TLS support. From this perspective, if I cannot > use C++ exceptions because of TLS and I have to use something else, then > another TLS-based library is not really an alternative. In this case it > does not matter that it is only IDs that are stored in TLS. The sole fact > of even employing TLS is a deal breaker. LEAF really only needs one thread-local pointer to the topmost context per thread, so it may be possible to replace the thread-local storage with a global lock-free hash table. A lock-free hash table only requires atomic support, which is generally available on GPUs and microcontrollers. The key of the hash table could be the thread id. Task-based RTOS systems could use its task handle instead. An example of a lock-free hash table: https://eourcs.github.io/LockFreeCuckooHash/

2 1

Re: [boost] [container] Proposal for ring queues
by Bjorn Reese 22 May '20

22 May '20

On 2020-05-22 00:17, Andrey Semashev via Boost wrote: > I would like to ask if there is interest in the community for these > kinds of containers. I know I would find them useful, and at least one > person commented in the PR to the same effect. However, I would still > like to see if more people need this. Do notice that we also have this proposal floating around: https://lists.boost.org/Archives/boost/2019/09/246925.php https://lists.boost.org/Archives/boost/2020/05/248871.php

2 1

Help sought with identifying failure cases on the boost.org test matrix
by Richard Hodges 22 May '20

22 May '20

Dear all, Looking here: https://www.boost.org/development/tests/master/developer/beast.html We're seeing a lot of yellow, but when I run tests locally I get 100% passes. I'm reaching out to anyone who might have information on how I can replicate the steps to failure, and then either fix the problem or help the test host correct the configuration, as appropriate. Many thanks for your time. -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

2 1