- Boost - lists.preview.boost.org

[release] Boost 1.78.0 Release Candidate 1
by Marshall Clow 03 Dec '21

03 Dec '21

The first release candidates for the 1.78.0 release are now available at: <https://boostorg.jfrog.io/artifactory/main/release/1.78.0/source/> The SHA256 checksums are as follows: 94ced8b72956591c4775ae2207a9763d3600b30d9d7446562c552f0a14a63be7 boost_1_78_0_rc1.tar.gz f22143b5528e081123c3c5ed437e92f648fe69748e95fa6e2bd41484e2986cc3 boost_1_78_0_rc1.zip 090cefea470bca990fa3f3ed793d865389426915b37a2a3258524a7258f0790c boost_1_78_0_rc1.7z 8681f175d4bdb26c52222665793eef08490d7758529330f98d3b29dd0735bccc boost_1_78_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

3 3

[release] Master branch now closed for 1.78.0 release
by Marshall Clow 02 Dec '21

02 Dec '21

Please do not make any commits to the master branch. — Marshall

1 0

[release] 1.78.0 post-beta merges
by Marshall Clow 01 Dec '21

01 Dec '21

The master branch is is now open for post-beta merges, but only as described in the Post-Beta Merge Policy. See <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy>> Reminder: The master branch closes for the release on Wednesday, December 1st. Full calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall P.S Doc changes and test changes do NOT require release manager approval to be merged.

11 36

[Release] The release branch will close for the 1.78.0 release TOMORROW
by Marshall Clow 01 Dec '21

01 Dec '21

As always, calendar is here: https://www.boost.org/development/index.html <https://www.boost.org/development/index.html> — Marshall

1 0

Re: [boost] boost.spawn: review requested
by Boris Kolpackov 30 Nov '21

30 Nov '21

Oliver Kowalke <oliver.kowalke(a)gmail.com> writes: > Am Mo., 29. Nov. 2021 um 15:54 Uhr schrieb Boris Kolpackov < > boris(a)codesynthesis.com>: > > > FWIW (and I may be out of context), but "spawn" seems like a > > too generic of a name. I, for example, thought this is about > > posix_spawn(). Maybe call it spawn_fiber or some such? > > > > boost.asio named the function spawn() - boost.spawn named it spawn_fiber() Sorry, looks I wasn't clear enough: I am talking about the library name being too generic: Boost.Spawn can mean spawning all kinds of things (processes, threads, fibers, etc). The fact that you called the function spawn_fiber() in a sense confirms this.

1 0

[fusion] add support for view construction from movable view
by herve martin 28 Nov '21

28 Nov '21

Hi, When working with view of boost::fusion I feel something frustrated because of the limited set of possible constructors. Indeed, apart from copy constructor, views usually only provide constructors taken l-value reference on sequence as input. I would like to extend the constructors set of views with some new ones which would also accept r-value references on view as input. This would allow some fancy combination at construction time as for example: vector <https://www.boost.org/doc/libs/1_77_0/libs/fusion/doc/html/fusion/container…><bool> v0(true);vector <https://www.boost.org/doc/libs/1_77_0/libs/fusion/doc/html/fusion/container…><int, char> v1(3, 'x');vector <https://www.boost.org/doc/libs/1_77_0/libs/fusion/doc/html/fusion/container…><std::string, int> v2("hello", 123); using view1 = joint_view< vector <https://www.boost.org/doc/libs/1_77_0/libs/fusion/doc/html/fusion/container…><int, char> , vector <https://www.boost.org/doc/libs/1_77_0/libs/fusion/doc/html/fusion/container…><std::string, int>>;using view = joint_view< vector <https://www.boost.org/doc/libs/1_77_0/libs/fusion/doc/html/fusion/container…><bool> , view1>; view aview = view(v0, view1(v1, v2));std::cout << aview << std::endl; I would be glad to contribute to the boost library by updating the boost::fusion views with some new constructors bu I'm not familiar with development in boost. What would be the next step to give a chance to my proposal to integrate boost ? Best regards, Herve

1 0

Adding my sorting algorithm, ska_sort, to boost, attempt 2
by Malte Skarupke 24 Nov '21

24 Nov '21

Hi everyone, I started a discussion about this in October, but at the time the maintainer of the sort library was busy, then I was busy, so now it's January... I wrote a generalized version of radix sort a couple years ago and gave a talk about it here: https://www.youtube.com/watch?v=zqs87a_7zxw I would like to get a new version of that sorting algorithm into boost. It's faster than what I showed several years ago. It's also even more general and has a new interface that should be easier to extend. I uploaded the code here: https://github.com/skarupke/sort/tree/master The documentation is also already updated with new benchmark results. Let me know what's required to get this into boost. Would you like this in the form of a pull request? One of the big things that probably needs review is the interface, since radix sorting works differently than comparison based sorting. For most normal uses you just need to provide a sort key, but more complicated cases can get more complicated. I tried very hard to make everything easy, but I'd also be curious if others can come up with better ways of doing the interface. Thanks, Malte -- Malte Skarupke malteskarupke(a)fastmail.fm

8 10

[release] 1.78.0 post-beta merges
by Oliver Kowalke 20 Nov '21

20 Nov '21

Hi, I'd like to merge several fixes for boost.context, boost.coroutine, boost.coroutine2 and boost.fiber to branch master. Oliver

2 1

Boost::any bad_any_cast issue
by rajesh daggumati 18 Nov '21

18 Nov '21

Hi Team, While doing typecasting from boost::any to DecodeErrorPayload_t, its throwing bad_any_cast .. class RegisterIONotification { public: enum NotifyType { TypeUnknown, TypeRegTx, TypeRegRx, TypeDecodeError }; NotifyType Type; boost::any Payload; typedef boost::tuple<std::string, BinaryBuffer_t> DecodeErrorPayload_t; RegisterIONotification(NotifyType type;,boost::any payload) { Type(type); Payload(payload); } }; I have called RegisterIONotification from other class function. void RegisterIOThreaded::OnDecodeError( const std::string& error, BinaryBuffer_t data ) { RegisterIONotification notify(RegisterIONotification::TypeDecodeError ,make_tuple(error, data)); ..... .... ... } While testing, I am getting bad_any_cast exception. TEST_F(...,...) { RegisterIONotification notify = sink.GetDataById(ID::NOTIFY_COMMS_STATUS, 0).GetValue<RegisterIONotification>(); ASSERT_EQ(RegisterIONotification::TypeDecodeError, notify.Type); //passed RegisterIONotification::DecodeErrorPayload_t payload; ASSERT_NO_THROW(payload = boost::any_cast<RegisterIONotification::DecodeErrorPayload_t>(notify.Payload));// Here its got failed…Please help me to fix this. } Regards, Rajesh D

2 1

ASIO problem with boost 1.78.0.beta1 ?
by Stefan Heinzmann 13 Nov '21

13 Nov '21

Hi all, I'm observing a problem with boost::asio that has surfaced with the newest beta relative to version 1.77.0, using MSVC 16.11.6. I'm getting the following errors: 1>...src\libs\asio\include\boost/asio/impl/any_io_executor.ipp(26,18): error C2039: 'any_io_executor': is not a member of 'boost::asio::executor' 1>...src\libs\asio\include\boost/asio/executor.hpp(48): message : see declaration of 'boost::asio::executor' 1>...src\libs\asio\include\boost/asio/impl/any_io_executor.ipp(26,34): error C2059: syntax error: ')' 1>...src\libs\asio\include\boost/asio/impl/any_io_executor.ipp(28,1): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int ...and so on. The errors seem rather weird to me, so I might be doing something wrong myself, but the exact same code compiles fine with 1.77.0, using the same compiler. Has anyone got an idea what's wrong? Should I raise an issue in github? Cheers Stefan Heinzmann

1 1