- Boost - lists.preview.boost.org

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

Re: [boost] Master branch is now open for bug fixes
by Дмитрий Архипов 02 Apr '23

02 Apr '23

1 0

Reminder: Release Notes
by Marshall Clow 30 Mar '23

30 Mar '23

If you’ve been meaning to write release notes for your library for the 1.82.0 release, now is the time to do it. ;-) — Marshall

1 0

Re: [boost] Master branch is now open for bug fixes
by Ruben Perez 30 Mar '23

30 Mar '23

On Thu, 16 Mar 2023 at 16:38, Marshall Clow via Boost <boost(a)lists.boost.org> wrote: > > The master branch is now open for bug fixes and documentation changes. I'd like to merge a UB fix to master for Boost.MySQL. It affects only debug builds. Not critical, but may hit some platforms. Discovered during development of new code. https://github.com/boostorg/mysql/pull/136 Thanks, Ruben.

2 1

Re: [boost] Master branch is now open for bug fixes
by Mojca Miklavec 30 Mar '23

30 Mar '23

On Thu, 16 Mar 2023 at 16: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> I would be really grateful if the following patch (or an alternative resolution for the reported warning/error) could be included in the final release: https://github.com/boostorg/thread/pull/382 (The only other warning we get in our project is https://github.com/boostorg/container/issues/234, but I'm not sure if one is allowed to modify dlmalloc_ext_2_8_6.c.) Quite some other warnings that we've been running into in 1.80 have disappeared in the meantime: thank you very much for that. Thank you very much, Mojca

1 0

Re: [boost] boost-1.82.0.beta1 tag looks wrong
by Marshall Clow 30 Mar '23

30 Mar '23

On Mar 29, 2023, at 8:57 AM, Peter Dimov via Boost <boost(a)lists.boost.org> wrote: > > commit ee18548b1eb68a592d0980611b5f96216ee71a2d (tag: boost-1.82.0.beta1) > Author: Automated Commit <automated(a)calamity.org.uk> > Date: Thu Mar 9 00:00:15 2023 +0000 > > Update multiprecision from develop > > Looks like the boost-1.82.0.beta1 tag points to develop rather than master. I think you’re right. The tag on the super project points to develop, and the one(s) on the sub-project all point to master. — Marshall

1 0

boost-1.82.0.beta1 tag looks wrong
by Peter Dimov 29 Mar '23

29 Mar '23

commit ee18548b1eb68a592d0980611b5f96216ee71a2d (tag: boost-1.82.0.beta1) Author: Automated Commit <automated(a)calamity.org.uk> Date: Thu Mar 9 00:00:15 2023 +0000 Update multiprecision from develop Looks like the boost-1.82.0.beta1 tag points to develop rather than master.

1 0

Re: [boost] Master branch is now open for bug fixes
by Jeff Trull 29 Mar '23

29 Mar '23

I'd like to merge a UB fix to master. It has (so far) not produced nasal demons, but is triggering checkers in projects that depend on Wave. https://github.com/boostorg/wave/pull/185 On Thu, Mar 16, 2023 at 8:38 AM 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> > > 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 >

2 1

Re: [boost] Master branch is now open for bug fixes
by Joaquin M López Muñoz 28 Mar '23

28 Mar '23

El 27/03/2023 a las 19:39, Peter Dimov via Boost escribió: > Joaquin M López Muñoz wrote: >> El 16/03/2023 a las 16:38, Marshall Clow via Boost escribió: >>> 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 >> Hi, I'd like to commit the following changes: >> >> * multi_index: removal of foreach and serialization from dependencies listed >> in CMakeLists.txt: >> https://github.com/boostorg/multi_index/commit/b6d5c88629d3ca3b0822e >> 87629c28ebf151c6a9e >> https://github.com/boostorg/multi_index/commit/0e55b4878952375c8f8c0 >> 0b6dc6964423644970e >> >> * flyweight: removal of serialization from dependencies listed in >> CMakeLists.txt: >> https://github.com/boostorg/flyweight/commit/b37873c46902f06d6c131a5 >> 25493ff6d29180efa > As a general reminder to everyone, if you make changes that add or remove > dependencies, and your CMakeLists.txt file is generated by `boostdep --cmake`, > and contains no further changes, you should regenerate it (by replacing it with > the output of `boostdep --cmake my_library`.) Thanks for the tip, I've just run boostdep and results coincide with what there's already on the CML files. Marshall, OK to merge to master? Joaquín M López Muñoz

2 1

Re: [boost] [scope] Proposing Boost.Scope
by Dominique Devienne 28 Mar '23

28 Mar '23

On Wed, Mar 22, 2023 at 2:41 AM Andrey Semashev via Boost < boost(a)lists.boost.org> wrote: > https://github.com/Lastique/scope Hi. Maybe you should tag your library on GitHub, so it can be easily found, among the several which "compete" with it. Like those listed at the link below: https://github.com/topics/scope-guard?l=c%2B%2B One in particular (https://github.com/offa/scope-guard) refers to the WG21 paper. PS: Actually, I wonder whether Boost Libraries in general use GH tagging much.

2 1