- Boost - lists.boost.org

boost.asem seeking endorsement
by Klemens Morgenstern 07 Mar '23

07 Mar '23

Heya Boost Community, I am seeking endorsement for my boost.asem library. It provides the following asio-based synchronization primitives: - barrier - condition_variable - mutex - semaphore Asio currently has timers & (experimental) channels that can help. However, I think there is a need for more purpose-made utilities to help more complex asio-based libraries (requests, redis, mysql et al.) Code: https://github.com/klemens-morgenstern/asem Docs: https://klemens.dev/asem/ I'm also not too happy with the name, but so far I only came up with an acronym: Semaphore, Condition_variable, And Mutex. Suggestions are welcome.

1 0

GSOC director stepping down and replacement
by Glen Fernandes 07 Mar '23

07 Mar '23

David Bellot who has run the Boost GSOC program is retiring from the role: Thank you David, for your service. If anyone wants to step forward and become the new GSOC administrator, Boost can keep the program running. David has generously agreed to help mentor his replacement until the transition is complete. If this sounds interesting to you, or if you have any questions about what the task entails, please don't hesitate to inquire further. Glen

1 0

Boost 1.82.0 is now closed for major changes
by Marshall Clow 05 Mar '23

05 Mar '23

Next deadline: On 8-Mar-2023 Boost 1.82.0 closes the beta release. Still open for serious problem fixes and docs changes without release manager review. As always, the release calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> - Boost release team

1 0

improve <boost/config.hpp>
by Gero Peterhoff 03 Mar '23

03 Mar '23

Hi, for more compatibility with existing boost-macros/defines I came up with - see attachment. 1) Is that correct in principle? 2) Problem: for BOOST_NO_CXX23_HDR_XXX I use __has_include. However, __has_include is not guaranteed to exist. How about the solution? 3) Did I miss useful things? thx Gero

6 6

Re: [boost] Has testing on msvc been dropped?
by Tom Kent 02 Mar '23

02 Mar '23

On Wed, Mar 1, 2023 at 6:13 AM Tom Kent via Boost <boost(a)lists.boost.org> wrote: > On Mon, Feb 27, 2023 at 6:16 AM Glen Fernandes <glen.fernandes(a)gmail.com> > wrote: > > > On Mon, Feb 27, 2023 at 6:49 AM Daniela Engert wrote: > > > >> I've noticed that e.g. Boost.Log no longer compiles on msvc 19.35 (i.e. > >> VS2022 update 5). Looking at the test matrix to figure out where the > >> problem might lie, I couldn't find any column with the test results of > >> *any* msvc version, lest the current one. Is there a reason for no > >> longer running the tests with msvc compilers? > >> > >> > > I don't believe it's intentional. > > > > Tom, do you know why the MSVC runners aren't reporting any results? > > > > Looks like my windows runner machine has crashed hard, I'm going to try to > resuscitate it. > It was a dead SSD, reinstalled with a brand-new windows OS, should be back up and cycling normally. In the meantime, I kicked off a set of runs on an Azure VM, so there should be stuff up now. Tom

2 1

Has testing on msvc been dropped?
by Daniela Engert 01 Mar '23

01 Mar '23

Hi y'all! I've noticed that e.g. Boost.Log no longer compiles on msvc 19.35 (i.e. VS2022 update 5). Looking at the test matrix to figure out where the problem might lie, I couldn't find any column with the test results of *any* msvc version, lest the current one. Is there a reason for no longer running the tests with msvc compilers? thank, Dani -- PGP/GPG: 2CCB 3ECB 0954 5CD3 B0DB 6AA0 BA03 56A1 2C4638C5

6 21

Re: [boost] Delivery Status Notification (Failure)
by Andre Marin 26 Feb '23

26 Feb '23

Hi, I'm interested in becoming a maintainer. I'm interested in the following projects: - Algorithm <https://www.boost.org/doc/libs/release/libs/algorithm/> - Python <https://www.boost.org/doc/libs/release/libs/python/> - Stl_interfaces <https://www.boost.org/doc/libs/release/libs/stl_interfaces/> - Type Erasure <https://www.boost.org/doc/libs/release/libs/type_erasure/> I'm trying to email olivas(a)icecube.umd.edu, per the Boost website but it's not going through. I'm looking for some guidance. I've included the previous request and email error in this email. Thank you, *Andre Marin * *m:* (832) 495-3545 *e:* andre(a)alexamarin.com <https://www.linkedin.com/in/andremarin629/> On Sun, Feb 26, 2023 at 11:46 AM Mail Delivery Subsystem < mailer-daemon(a)googlemail.com> wrote: > [image: Error Icon] > Address not found > Your message wasn't delivered to *olivas(a)icecube.umd.edu* because the > address couldn't be found, or is unable to receive mail. > The response from the remote server was: > > 550 5.1.1 <olivas(a)icecube.umd.edu>: Recipient address rejected: User > unknown in local recipient table > > > > ---------- Forwarded message ---------- > From: Andre Marin <andre(a)alexamarin.com> > To: olivas(a)icecube.umd.edu > Cc: > Bcc: > Date: Sun, 26 Feb 2023 11:46:03 -0600 > Subject: Boost Library Official Maintainer Program > Hi, > > I'm interested in becoming a maintainer. I'm interested in the following > projects: > > - Algorithm <https://www.boost.org/doc/libs/release/libs/algorithm/> > - Python <https://www.boost.org/doc/libs/release/libs/python/> > - Stl_interfaces > <https://www.boost.org/doc/libs/release/libs/stl_interfaces/> > - Type Erasure > <https://www.boost.org/doc/libs/release/libs/type_erasure/> > > > I've been limited to C++11 at work and I'm new to library contributions. > I'm not sure if there are more appropriate projects for noobs or areas of > need I couldn't find on the website. > > Thank you, > > *Andre Marin * > *m:* (832) 495-3545 > *e:* andre(a)alexamarin.com > <https://www.linkedin.com/in/andremarin629/> >

2 1

Future of boost::TypeTraits
by Gero Peterhoff 24 Feb '23

24 Feb '23

Hello, with the planned changes of the dependencies of the boost libraries to newer C++-standards, I would like to ask how this is planned for boost::TypeTraits. 1) In my opinion it would make sense to remove all TypeTraits that are already in the standard, and only provide those that do not exist in the standard (yet). Of course, this depends on the planned minimum standard for boost::TypeTraits. 2) If, on the other hand, boost::TypeTraits is to continue to work with C++03 (for which there may be reasons), however, quite a few adjustments must be made (for newer C++-standards) and bugs must be fixed. Examples: a) - no inline-variables are provided for C++17 (if useful), e.g. is_arithmetic_v - no concepts are provided for C++20 (if useful), e.g. arithmetic - that's why I already asked how to do this best without coming into (name)conflicts with existing structures/namespaces/etc. b) bugs - e.g. is_integral does not contain char8_t (if available) Probably my remarks also apply to other libraries, possibly TypeErasure, TypeIndex, TTI ... All this has to be reworked fundamentally and consolidated if necessary. best regards Gero

1 0

Boost Libraries and Dropping C++ Language Support
by Glen Fernandes 24 Feb '23

24 Feb '23

*Boost library authors and maintainers are free to drop support for old C++ standards in their libraries, at any time. * This includes libraries that other Boost libraries depend on. It even includes core libraries like Boost.Core or Boost.Static_Assert. We ask that maintainers do the right thing by all our users (which may include other Boost libraries) by announcing a future breakage *at least two Boost releases in advance*. When that eventual release time arrives, if Boost libraries are broken in older standards modes due to another Boost library dropping support, it will not block the Boost release. This means that we do not need to announce "Boost is dropping C++03" because Boost doesn't "support C++03" now as it is. It means that you, maintainer of Boost.X, should realize that you are free to announce that "Boost.X is dropping C++XY in version 1.Z" as you see fit. Boost in its infancy thrived because its libraries were on the cutting edge. Boost libraries today should similarly not be confined simply because other Boost libraries have chosen to depend on them. Furthermore, as Boost release managers we support authors exercising this freedom, and do not intend to impose any restrictions on what language support they must maintain. We will add a page to the Boost website stating the above formally. -- The release team (Glen Fernandes, Marshall Clow)

8 12

Boost 1.82.0 is now closed for new libraries and breaking changes
by Marshall Clow 23 Feb '23

23 Feb '23

Next deadline: On 1-Mar-2023 Boost 1.82.0 closes for major code changes. Still open for serious problem fixes and docs changes without release manager review. As always, the release calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> - Boost release team

1 0