April 2023 - Boost - lists.boost.org

[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 06 Apr '23

06 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 04 Apr '23

04 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

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

03 Apr '23

On Apr 3, 2023, at 2:38 AM, Andrey Semashev via Boost <boost(a)lists.boost.org> wrote: > > On 4/1/23 14:06, Andrey Semashev wrote: >> On 3/16/23 18:38, 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/> >> >> I would like to merge the following commit to Boost.Filesystem master: >> >> https://github.com/boostorg/filesystem/commit/1db4474d1ae7512af06f63156352f… >> >> It works around a problem on Windows caused by incorrect reporting of >> file attributes for directories in SMBv1 shares. > > Ping? Go ahead — Marshall

1 0

Re: [boost] Master branch is now open for bug fixes
by Andrey Semashev 03 Apr '23

03 Apr '23

On 3/16/23 18:38, 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/> I would like to merge the following commit to Boost.Filesystem master: https://github.com/boostorg/filesystem/commit/1db4474d1ae7512af06f63156352f… It works around a problem on Windows caused by incorrect reporting of file attributes for directories in SMBv1 shares.

1 1

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

03 Apr '23

On Apr 2, 2023, at 12:43 PM, Дмитрий Архипов via Boost <boost(a)lists.boost.org> wrote: > > I would like to merge the following commits to Boost.JSON master: > > Updated documentaion: > https://github.com/boostorg/json/commit/ee01580cfde818e31d8ea41c2e4056bcff9… > 1.82.0 release notes > https://github.com/boostorg/json/commit/94c5d74710ee68301a524e3bc0ed50ec7bd… > document string SBO > https://github.com/boostorg/json/commit/33088c958a635db87299e9c26db12c3c689… > example of using string::grow > https://github.com/boostorg/json/commit/aa77d906396394177b1b34620bd47d9763e… > provide example of parsing several values from several buffers > https://github.com/boostorg/json/commit/32e1d52cdd3f30266a29b99bd4ef456e8a7… > document supported JSON > https://github.com/boostorg/json/commit/4a7a2034d9a5c3d2f3798a5b352e7946504… > fix overview sectioning > https://github.com/boostorg/json/commit/b6a6c83dc740700d74a2f1a38a44c1cb9f1… > document potential linking requirements > https://github.com/boostorg/json/commit/7cf7f107f6913dd3ae61428c7314a19c459… > mention RFC in overview and README > https://github.com/boostorg/json/commit/87b97a09903b37673b2ceb2ae3a2b6ff031… > a JSON to a JSON text You don’t need permission for documentation fixes. > https://github.com/boostorg/json/commit/274901f3488e6ed7cf180f9167dccb22118… > fix template parameter docs for make_shared_resource This is fine. > https://github.com/boostorg/json/commit/89bc551d8214b6c32fa6d161f13e3aaad84… > clarify what default memory resource is > https://github.com/boostorg/json/commit/d7b0580befd3d7fe8ee0b093b96edbfb259… > mention how to disable autolinking These are doc fixes - no permission necessary. > > Bug fix: > https://github.com/boostorg/json/commit/9b06d4a4107f7df58a516987474705fef88… > fix suspend inside escape This is fine. > > Silencing a warning: > https://github.com/boostorg/json/commit/d79336bbb7cb49e396db37c8547daca1e61… > Fix -Wdeprecated-declarations for sprintf This is fine. — Marshall > > > > чт, 16 мар. 2023 г. в 18:38, Marshall Clow via Boost <boost(a)lists.boost.org >> : > >> 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