March 2023 - Boost - lists.preview.boost.org

Re: [boost] Master branch is now open for bug fixes
by Marshall Clow 22 Mar '23

22 Mar '23

On Mar 21, 2023, at 6:34 PM, Klemens Morgenstern via Boost <boost(a)lists.boost.org> wrote: > > I would like to ask permission to merge this minor fix: > https://github.com/boostorg/beast/pull/2659 <https://github.com/boostorg/beast/pull/2659> > If the tests have cycled, and you’re happy with the results, then go ahead. — Marshall

1 0

[scope] Proposing Boost.Scope
by Andrey Semashev 22 Mar '23

22 Mar '23

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. Thank you.

1 0

Re: [boost] Master branch is now open for bug fixes
by Klemens Morgenstern 22 Mar '23

22 Mar '23

I would like to ask permission to merge this minor fix: https://github.com/boostorg/beast/pull/2659 On Wed, Mar 22, 2023 at 7:44 AM Marshall Clow via Boost < boost(a)lists.boost.org> wrote: > > > > On Mar 21, 2023, at 10:48 AM, Antony Polukhin via Boost < > boost(a)lists.boost.org> wrote: > > > > On Thu, Mar 16, 2023, 18:38 Marshall Clow via Boost < > boost(a)lists.boost.org> > > wrote: > > > >> The master branch is now open for bug fixes and documentation changes. > >> Other changes by release manager permission, as described in > >> > >> https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < > >> https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy> > >> > > > > Sorry, I've misread the message and applied a "bug fix" without reading > the > > wiki, where "Code changes and fixes" should be merged only after release > > manager permission. > > > > May I keep the bugfix > > > https://github.com/boostorg/stacktrace/commit/d904d26f4f5998fc1488e964a37e6… > > for the stacktrace merged to master branch? > > > > Thanks for letting us know. > The commit looks fine to me. > > — Marshall > > > > > The fix was in develop for two months and it switches > > backtrace_create_state into thread safe mode if platform supports > > multithreading. > > > >> > > > > _______________________________________________ > > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

1 0

Re: [boost] Master branch is now open for bug fixes
by Marshall Clow 21 Mar '23

21 Mar '23

> On Mar 21, 2023, at 10:48 AM, Antony Polukhin via Boost <boost(a)lists.boost.org> wrote: > > On Thu, Mar 16, 2023, 18:38 Marshall Clow via Boost <boost(a)lists.boost.org> > wrote: > >> The master branch is now open for bug fixes and documentation changes. >> Other changes by release manager permission, as described in >> >> https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < >> https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy> >> > > Sorry, I've misread the message and applied a "bug fix" without reading the > wiki, where "Code changes and fixes" should be merged only after release > manager permission. > > May I keep the bugfix > https://github.com/boostorg/stacktrace/commit/d904d26f4f5998fc1488e964a37e6… > for the stacktrace merged to master branch? > Thanks for letting us know. The commit looks fine to me. — Marshall > The fix was in develop for two months and it switches > backtrace_create_state into thread safe mode if platform supports > multithreading. > >> > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] Master branch is now open for bug fixes
by Antony Polukhin 21 Mar '23

21 Mar '23

On Thu, Mar 16, 2023, 18:38 Marshall Clow via Boost <boost(a)lists.boost.org> wrote: > The master branch is now open for bug fixes and documentation changes. > Other changes by release manager permission, as described in > > https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy < > https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy> > Sorry, I've misread the message and applied a "bug fix" without reading the wiki, where "Code changes and fixes" should be merged only after release manager permission. May I keep the bugfix https://github.com/boostorg/stacktrace/commit/d904d26f4f5998fc1488e964a37e6… for the stacktrace merged to master branch? The fix was in develop for two months and it switches backtrace_create_state into thread safe mode if platform supports multithreading. >

1 0

Re: [boost] Master branch is now open for bug fixes
by Marshall Clow 21 Mar '23

21 Mar '23

On Mar 21, 2023, at 8:59 AM, Samuel DEBIONNE via Boost <boost(a)lists.boost.org> wrote: > > Hello, > I would like to merge a "missing include" fix from Boost.GIL to master: > > https://github.com/boostorg/gil/pull/729 Go ahead — Marshall > > Thank you, > Samuel > On 16/03/2023 16:43, Marshall Clow via Boost wrote: >> The master branch is now open for bug fixes and documentation changes. >> Other changes by release manager permission, as described in >> https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy> >> The next deadline: On April 5th, master closes for all changes. >> As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> >> — Marshall >> _______________________________________________ >> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] Master branch is now open for bug fixes
by Samuel DEBIONNE 21 Mar '23

21 Mar '23

Hello, I would like to merge a "missing include" fix from Boost.GIL to master: https://github.com/boostorg/gil/pull/729 Thank you, Samuel On 16/03/2023 16:43, Marshall Clow via Boost wrote: > The master branch is now open for bug fixes and documentation changes. > Other changes by release manager permission, as described in > https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy> > > The next deadline: On April 5th, master closes for all changes. > > As always, the calendar is at https://www.boost.org/development/ <https://www.boost.org/development/> > > — Marshall > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] Need Volunteers for Docs!
by Ruben Perez 19 Mar '23

19 Mar '23

On Sat, 18 Mar 2023, 01:55 Vinnie Falco via Boost, <boost(a)lists.boost.org> wrote: > > Documentation has been a long-running complaint of users and authors. > The look of it, the content of it, and the way that people find it. We > are looking to resolve all of that and we've made quite a lot of > progress but we need help. There's a ton of work going into the > infrastructure and website right now so if you want to be a part of it > please speak up! > You know my obsession with docs, so I volunteer. Please let me know how can I help. Ruben. > >

2 1

Re: [boost] Need Volunteers for Docs!
by Vinnie Falco 18 Mar '23

18 Mar '23

On Fri, Mar 17, 2023 at 6:07 PM Klemens Morgenstern via Boost <boost(a)lists.boost.org> wrote: > I've been writing the occasional post on cppalliance.org, should that go to > boost instead? Or should boost operate like an aggregator? There's no facility for blogging yet but there will be on the new Boost website (and it will use Asciidoc). This will take a while though since it is not a planned feature for the initial release. This will also come with a way to post off-site links (like an aggregator) but since https://cpp.al is not receiving heavy traffic it would make more sense to migrate the blog content from there to the new boost.org. Thanks

1 0

Re: [boost] Need Volunteers for Docs!
by Klemens Morgenstern 18 Mar '23

18 Mar '23

I've been writing the occasional post on cppalliance.org, should that go to boost instead? Or should boost operate like an aggregator? On Sat, Mar 18, 2023 at 8:55 AM Vinnie Falco via Boost < boost(a)lists.boost.org> wrote: > All: > > We are working on the User's Guide which is for people who want to use > Boost, and we are working on the Contributor's guide which is for > people who want to contribute to Boost. This includes authors, > maintainers, reviewers, review managers, review wizards, release > managers, contributors, testers, basically everyone who is changing > the state of our repositories somehow. > > These manuals are written in Asciidoc, but we need volunteers who can > jump in and start producing results right away. Most of the existing > site content has been ported to markdown and it needs editing and > sorting into a table of contents. The Getting Started instructions > which go into the release are in pretty rough shape and need editing. > > Documentation has been a long-running complaint of users and authors. > The look of it, the content of it, and the way that people find it. We > are looking to resolve all of that and we've made quite a lot of > progress but we need help. There's a ton of work going into the > infrastructure and website right now so if you want to be a part of it > please speak up! > > This is a sample of where we are going with it (the stylesheets have > not been worked on yet): > > https://antora.cppalliance.org/doc/html/mp11/mp11/list.html > > https://antora.cppalliance.org/doc/html/contributor-manual/intro.html > > Thank you for considering it ! > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

1 0