- Boost - lists.preview.boost.org

Re: [boost] Request to merge bug fixes in Boost.Outcome
by Niall Douglas 25 Jul '23

25 Jul '23

On 20/07/2023 11:36, Niall Douglas wrote: > Can I get permission to merge a few small bug fixes plus docs fixes? > > https://github.com/boostorg/outcome/commits/develop > > 1. Changes just before the beta window breaks build on C++ 14 in certain > corner cases, fixed. > > 2. Experimental Outcome Boost result did not compile due to changes to > status code by LEWG, fixed. > > 3. Docs fixes also due to the LEWG renaming breaking docs examples. > > 4. Failure to compile Experimental Outcome on FreeBSD fixed. Ping on the above. Niall

2 2

Bug fixes in Boost.URL
by Alan de Freitas 21 Jul '23

21 Jul '23

I would like to ask for permission to merge the following bug fixes to master in Boost.URL: - c97bc278: parse_query does not recreate string_view - 0ca58467: url_view string_view constructor requires non-url_view_base - f2bb191b: IP-literal can be IPv6addrz Thanks -- Alan Freitas https://alandefreitas.github.io/alandefreitas/ <https://github.com/alandefreitas>

2 1

Request to merge bug fixes in Boost.Outcome
by Niall Douglas 20 Jul '23

20 Jul '23

Can I get permission to merge a few small bug fixes plus docs fixes? https://github.com/boostorg/outcome/commits/develop 1. Changes just before the beta window breaks build on C++ 14 in certain corner cases, fixed. 2. Experimental Outcome Boost result did not compile due to changes to status code by LEWG, fixed. 3. Docs fixes also due to the LEWG renaming breaking docs examples. 4. Failure to compile Experimental Outcome on FreeBSD fixed. Niall

2 1

boost::normal_distribution<>(boost::mt19937) changed behavior from 1.60 to 1.80
by Foelsche, Peter 18 Jul '23

18 Jul '23

Dear All, I'm not certain if the behavior I'm seeing is expected or a problem. I'm getting different series of numbers from the two different boost versions in question. When running a diff on the output I'm getting numbers inserted in one series or the other and then the two series become identical again. Below is the source. I'm using the following series of commands: g++ -std=c++14 test.cpp -g -DNDEBUG -fwhole-program -I/mnt/share/boost/boost-1.80/include -o 180 g++ -std=c++14 test.cpp -g -DNDEBUG -fwhole-program -o 160 ./180 16384 2078781393 1 > 180.txt ./160 16384 2078781393 1 > 160.txt diff 160.txt 180.txt |more The first difference is at line 284. The next at 364, 1783, 2685. Peter PS. g++ (GCC) 5.3.0 PPS. The source #include <boost/random.hpp> #include <boost/version.hpp> //#include <boost/random/variate_generator.hpp> #include <boost/random/mersenne_twister.hpp> #include <boost/random/normal_distribution.hpp> #include <boost/random/uniform_int_distribution.hpp> #include <limits> #include <iostream> int main(int, char**argv) { std::cout << BOOST_LIB_VERSION << std::endl; const auto bOld = std::atoi(argv[3]) != 0; boost::mt19937 sGenerator; sGenerator.seed(std::atoi(argv[2])); //boost::random::uniform_int_distribution<> sDist(0, std::numeric_limits<int>::max()); boost::normal_distribution<> sDist(0.0, 1.0); boost::variate_generator<boost::mt19937, boost::normal_distribution<> > sGen(sGenerator, sDist); for (int i = 0, iMax = std::atoi(argv[1]); i < iMax; ++i) if (bOld) std::cout << sDist(sGenerator) << std::endl; else std::cout << sGen() << std::endl; }

2 1

Boostorg GitHub now has unlimited private repositories and collaborators
by Glen Fernandes 17 Jul '23

17 Jul '23

Boostorg GitHub now has unlimited private repositories and collaborators. Glen

1 0

Request to fix docs mistake in Boost.Outcome
by Niall Douglas 16 Jul '23

16 Jul '23

I know the beta release is happening, but when it's out and master branch is reopened can I get permission to merge a mistake in documentation fixed by https://github.com/ned14/outcome/issues/280? Niall

4 8

[1.83][type_erasure] Permission to merge to master
by Joaquín M López Muñoz 14 Jul '23

14 Jul '23

Hi, I’d like to merge this to master: https://github.com/boostorg/type_erasure/compare/master...develop This is a fix for issue #20: https://github.com/boostorg/type_erasure/issues/20 Plus some CI machinery kindly provided by Peter Dimov. Tests pass 100% on develop. Thank you, Joaquín M López Muñoz

2 1

[Release] Master branch is closed for beta
by Marshall Clow 13 Jul '23

13 Jul '23

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html <https://www.boost.org/development/index.html> -- Release managers

2 3

[release] Boost 1.83.0 beta 1 released
by Marshall Clow 13 Jul '23

13 Jul '23

Boost release 1.83.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.83.0.beta1/source/ The SHA256 checksums are: 69fe7224568acfa5491bfaa04fd522bf7cfca1800aa192de96ce560da714902f boost_1_83_0_b1.7z 49afc7c20d65949f7b775060bbec403e7e81d207949dd9f412e2d4569ea5d3f7 boost_1_83_0_b1.zip fe3895ee9ac78cf57328415f1b3bf3da7ea2ccb3ad87bf0d9b720910d99d18ae boost_1_83_0_b1.tar.bz2 fbbe0d439db5b65f194eb61b89b5cda0575387b0b23fbb85900c3c9ef9eb64bf boost_1_83_0_b1.tar.gz There was one bug reported during the beta process; Boost.Context does not build on ARM64 systems. This will be fixed for the final release. If you want to fix it locally, edit the file libs/context/build/Jamfile.v2: - else if [ os.platform ] = "ARM" { tmp = aapcs ; } + else if [ os.platform ] in ARM ARM64 { tmp = aapcs ; } The web site has not yet been updated (tomorrow, I hope) but when it is, the release notes will be at: https://www.boost.org/users/history/version_1_83_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

1 0

New Website Clarification
by Vinnie Falco 11 Jul '23

11 Jul '23

In this recent reddit post, Jonathan (online nickname "foonathan") says: > AFAIK the CppAlliance decided to unilaterally write a > new boost website for the Boost foundation, but the Boost > foundation wasn't/isn't that interested in it. > ... > I was told details, but I don't know whether they are official > Boost foundation statements or personal views of the person > that told me about it, so I don't want to share them. https://www.reddit.com/r/cpp/comments/14whxvd/comment/jriii9h/ I responded with a clarification which I am reposting here for the convenience of the folks on the mailing list. Cut on the dotted line: Thanks ---- Point of clarification here: We (a collection of Boost library authors including myself) recognized the need for an updated website. Discussions about a new website would recur on the mailing list, with everyone offering different opinions. There were one (maybe two? efforts to produce a new website which started out with good intentions but ultimately failed for various reasons (venturing a guess I would say that it was a "design by committee" problem combined with a lack of resources). The current new in-development website is here (the URL is temporary): https://boost.revsys.dev Please open any issues or requests in the corresponding site repo: https://github.com/cppalliance/temp-site Because I care about Boost and I am deeply committed to improving the C++ ecosystem, I decided that The C++ Alliance would invest its resources in a new website project, following these principles: That we would start building the site first instead of starting with lengthy mailing list discussions that go nowhere. That the new site would be designed according a vision that was later outlined in a mailing list post (see: https://lists.boost.org/Archives/boost/2023/05/254612.php) *After* the site was substantially completed we would launch a public beta to get feedback on what areas we need to work on. That we would leave to the Boost community: the library authors, maintainers, reviewers, release managers, and users; the decision on whether the new website is what they want to represent Boost going forward. In other words I took the approach to simply build it first and then figure out what people want later. Because the mailing list tradition is to debate a thing intensely and then proceed to do nothing as no one is interesting in actually doing the work. Of course I recognized and accepted before the project was started that this could be one huge gamble; that no one is going to want this type of site, and that most everyone prefers the existing site. I can understand the Boost Foundation's reluctance to embrace this new website. Creating, maintaining, and hosting something of this high level of quality requires resources. Fortunately, The C++ Alliance is well equipped for the task. To ensure the ongoing success of this website we have allocated in our budget ongoing full-time staff as well as the resources to ensure that the website is performant for visitors in every timezone (as Boost has a global audience). Our dedicated website staff includes: Samuel Darwin: Our full-time CTO/Senior DevOps expert. He is the guy who deployed Drone CI and make it available for the entire Boost GitHub organization (example: https://drone.cpp.al/boostorg/url) He brings decades of experience managing live systems and has been studying intensely on the specific needs of C++ developers Spencer Strickland: Our full-time front-end developer who is up-to-date on modern, responsive website development. He is also a programming enthusiast who loves writing JavaScript and Python programs. He is also working on styling the templates for the new documentation toolchain (example: https://www.boost.revsys.dev/doc/user-guide/task-networking.html) Peter Turcan: Our full time technical writer. He's furiously typing away at brand new documentation for Boost users and authors. As documentation complaints are a recurring theme from users, we feel that having at least one dedicated technical writer is probably a good start! You can check out his work here: https://www.boost.revsys.dev/doc/contributor-guide/version-control.html We also keep an ongoing maintenance contract with RevSys (https://www.revsys.com/) a wonderful development company whose founder (Frank Wiles) specializes in Django and is also responsible for contributing a huge percentage of the work that went into the Django project itself. Only the best for Boost! And don't forget you can visit all of us at The C++ Alliance, plus many Boost library authors, maintainers, and users, and many prominent members of the C++ community including some Standardization Committee regulars, by joining the Official C++ Language Slack Workspace at: https://cppalliance.org/slack/ The C++ Alliance sponsors this workspace by offering a complete Paid Plan which allows unlimited full history, uploads, video and audio recordings, and video and audio huddles/group chats for collaboration and more. Visit us today!

2 1