- Boost - lists.boost.org

Re: [boost] [release] Boost 1.82.0 Release Candidate 1 is available
by Ruben Perez 06 Apr '23

06 Apr '23

I have successfully built the RC in Ubuntu 22.04 and clang-15. I'd like however to flag commit https://github.com/boostorg/asio/commit/19cff007b0e9bf78dad921fe2a390d34589… that was merged into Boost.Asio's master branch on the 5th of April and hasn't gone into this RC as breaking existing code (concretely, this prevents some Boost.MySQL examples from compiling). It was caught by chance by a CI run. If this commit gets merged into any subsequent 1.82 RC, Boost.MySQL (and potentially other user code) will contain flaws. This commit breaks the following code: // Token declaration constexpr auto token = asio::as_tuple(asio::use_awaitable); // In a C++20 coroutine co_await socket.async_read(buffer, token); I don't know if this was meant to be legal or not, but used to build and run fine until yesterday. I can provide a fix if this commit gets merged into any subsequent RC, but other client code may get affected. Regards, Ruben. On Thu, 6 Apr 2023 at 16:54, Marshall Clow via Boost <boost(a)lists.boost.org> wrote: > > On Apr 6, 2023, at 7:25 AM, Marshall Clow via Boost <boost(a)lists.boost.org> wrote: > > > > The first release candidates for the 1.82.0 release are now available at: > > <https://boostorg.jfrog.io/artifactory/main/release/1.82.0/source/> > > > > The SHA256 checksums are as follows: > > > > b6bfc8adc9056bdb01083680b77ecdd7ad4a59a7425a3a42e15a1fe7f6c4f459 boost_1_82_0_rc1.7z > > 891aa0d522f80d79ecf622378961ceec882025d55b8aa85f61847db602056d57 boost_1_82_0_rc1.zip > > bcdf29d00ade098140ef6934849f27273ad655fcb1e172a4f25660ae0f930d33 boost_1_82_0_rc1.tar.gz > > 17d717a04d81e4e23bf0b527bae894f36db72c75976224ddedea9ffddfcd1fbd boost_1_82_0_rc1.tar.bz2 > > > > > > As always, the release managers would appreciate it if you download the > > candidate of your choice and give building it a try. Please report both > > success and failure, and anything else that is noteworthy. > > > I have successfully built the libraries in Mac OS 12.6.4, > with "Apple clang version 14.0.0 (clang-1400.0.29.202)” > and C++ 03/11/14/17/20/2b, on both x86 and ARM. > > — Marshall > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] [release] Boost 1.82.0 Release Candidate 1 is available
by Marshall Clow 06 Apr '23

06 Apr '23

On Apr 6, 2023, at 7:25 AM, Marshall Clow via Boost <boost(a)lists.boost.org> wrote: > > The first release candidates for the 1.82.0 release are now available at: > <https://boostorg.jfrog.io/artifactory/main/release/1.82.0/source/> > > The SHA256 checksums are as follows: > > b6bfc8adc9056bdb01083680b77ecdd7ad4a59a7425a3a42e15a1fe7f6c4f459 boost_1_82_0_rc1.7z > 891aa0d522f80d79ecf622378961ceec882025d55b8aa85f61847db602056d57 boost_1_82_0_rc1.zip > bcdf29d00ade098140ef6934849f27273ad655fcb1e172a4f25660ae0f930d33 boost_1_82_0_rc1.tar.gz > 17d717a04d81e4e23bf0b527bae894f36db72c75976224ddedea9ffddfcd1fbd boost_1_82_0_rc1.tar.bz2 > > > As always, the release managers would appreciate it if you download the > candidate of your choice and give building it a try. Please report both > success and failure, and anything else that is noteworthy. I have successfully built the libraries in Mac OS 12.6.4, with "Apple clang version 14.0.0 (clang-1400.0.29.202)” and C++ 03/11/14/17/20/2b, on both x86 and ARM. — Marshall

1 0

[release] Boost 1.82.0 Release Candidate 1 is available
by Marshall Clow 06 Apr '23

06 Apr '23

The first release candidates for the 1.82.0 release are now available at: <https://boostorg.jfrog.io/artifactory/main/release/1.82.0/source/> The SHA256 checksums are as follows: b6bfc8adc9056bdb01083680b77ecdd7ad4a59a7425a3a42e15a1fe7f6c4f459 boost_1_82_0_rc1.7z 891aa0d522f80d79ecf622378961ceec882025d55b8aa85f61847db602056d57 boost_1_82_0_rc1.zip bcdf29d00ade098140ef6934849f27273ad655fcb1e172a4f25660ae0f930d33 boost_1_82_0_rc1.tar.gz 17d717a04d81e4e23bf0b527bae894f36db72c75976224ddedea9ffddfcd1fbd boost_1_82_0_rc1.tar.bz2 As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

1 0

[release] Master Branch is closed for all changes
by Marshall Clow 06 Apr '23

06 Apr '23

Please do not commit anything to the master branch. Other branches are always fine. The 1.82.0 release is scheduled for next Wednesday, 13-Apr. — Marshall

1 0

Re: [boost] I need help with clang libtooling
by Boris 05 Apr '23

05 Apr '23

On 2023-04-05 6:43 PM, Vinnie Falco via Boost wrote: > On Wed, Apr 5, 2023 at 1:00 AM Boris via Boost <boost(a)lists.boost.org> wrote: >> I have some experience, I created https://github.com/scapix-com/scapix >> with clang libtooling. You can ask me directly or in the list. > Can we please set up some kind of screen share / zoom / chat or something? Sure, I will email you directly to set it up.

1 0

Re: [boost] I need help with clang libtooling
by Vinnie Falco 05 Apr '23

05 Apr '23

On Wed, Apr 5, 2023 at 1:00 AM Boris via Boost <boost(a)lists.boost.org> wrote: > I have some experience, I created https://github.com/scapix-com/scapix > with clang libtooling. You can ask me directly or in the list. Can we please set up some kind of screen share / zoom / chat or something? Thanks

1 0

[release] Reminder: The master branch will be closing for the 1.82.0 release TODAY
by Marshall Clow 05 Apr '23

05 Apr '23

… and don’t forget your release notes! — Marshall

1 0

Re: [boost] I need help with clang libtooling
by Boris 05 Apr '23

05 Apr '23

On 2023-04-05 3:09 AM, Vinnie Falco via Boost wrote: > Does anyone know clang libtooling at all who can possibly help me? I > have my program mostly working but there are a few fine details I am > missing... > > Thanks > I have some experience, I created https://github.com/scapix-com/scapix with clang libtooling. You can ask me directly or in the list. Boris.

1 0

I need help with clang libtooling
by Vinnie Falco 05 Apr '23

05 Apr '23

Does anyone know clang libtooling at all who can possibly help me? I have my program mostly working but there are a few fine details I am missing... Thanks -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

1 0

Re: [boost] [scope] Proposing Boost.Scope
by Andrzej Krzemienski 03 Apr '23

03 Apr '23

śr., 22 mar 2023 o 02:49 Andrey Semashev via Boost <boost(a)lists.boost.org> napisał(a): > Hi, > > I'm proposing a Boost.Scope library for review and potential inclusion > into Boost. > > Boost.Scope is a small library implementing utilities defined in > <experimental/scope> from C++ Extensions for Library Fundamentals v3 > with a few extensions. Namely, the library contains: > > * A number of scope guards for various use cases. > * A unique resource wrapper that automatically frees the resource on > destruction. > * Utilities for wrapping POSIX-like file descriptors in the unique > resource wrapper. > > Compared to <experimental/scope>, some notable extensions are: > > * A new scope_final scope guard, which is a more lightweight alternative > to scope_exit. It is accompanied with the BOOST_SCOPE_FINAL macro that > allows to simplify scope guard declaration syntax. > * Scope guards can be activated/deactivated multiple times. > * Scope guards can be created inactive initially. > * Scope guard factory functions, for compatibility with C++11. > * Support for optional resource traits in unique_resource wrapper, which > improves usage with resources having unallocated values. > * unique_resource supports swapping. > * unique_resource supports dereferencing for any resource types that > support dereferencing, not only pointers. > * More flexible constructors for unique_resource. > > The library requires C++11 at the minimum and will significantly benefit > from C++17. > > Source: > > https://github.com/Lastique/scope > > Docs: > > https://lastique.github.io/scope/libs/scope/doc/html/index.html > > Current state: Feature complete, tested in the CI. > > I'm asking for a review manager and endorsements. > > I'm also looking forward for any pre-review comments. In particular, I'm > interested in community opinion on the following: > > * Is there interest in this library at all? > * Should it be merged with Boost.ScopeExit, which is currently > unmaintained? More on this below. > * Should some/all of the library components be lifted to namespace > boost? Such is the practice with most vocabulary types in Boost, e.g. > boost::atomic, boost::shared_ptr, boost::any, boost::string_view, etc. > Currently, the library defines its names in namespace boost::scope. > * Comments on the resource traits feature are especially welcome. > > Re. Boost.ScopeExit. There is significant functionality overlap with it > in the scope guards department. The docs contain comparison with it. I > believe there is room for both libraries because Boost.ScopeExit > supports C++03 and Boost.Scope provides better syntax and more features, > and both can be useful in their own regards, although I expect > Boost.Scope to be more appealing in newer code bases. However, if the > community decides there's too much overlap, I'm not opposed to merging > the two libraries, although Boost.ScopeExit currently depends on > Boost.Function, Boost.Preprocessor and Boost.TypeOf, which are > unnecessary for Boost.Scope. > Is there a single-header version of this library? So that we could easily test it in the Compiler Explorer? Regards, &rzej;

2 1