- Boost - lists.boost.org

Re: [boost] Regression tests not updating
by Nikita Kniazev 27 Aug '21

27 Aug '21

> What do you suggest as a solution? I agree that autodetection with no > way to override it is bad. (In my not yet finished CMake guidelines, I > advocate for only using autodetection to determine the default for > the configuration option, while still allowing the user to override it.) > But how does this translate to something actionable? How would you > have written the Nowide build/Jamfile? Sigh, if I had a good solution I would have presented it. An easiest and no-brainer way to tackle this is to have a per-library variable `is-boost-<library>-required/optional` on which library would have to omit checks (do not import Boost.Config, and do not pass checks that return `<build>no` to project/library requirements): ``` if is-boost-<library>-optional { import ../../config/checks/config : requires ; $(do-not-build-if) = [ requires ... ] ; } lib boost_<library> : ... : $(do-not-build-if) ; ``` However, in my opinion, a library must never add `<build>no` to its requirements by itself. Something external should decide if the build/checks failure is fatal or not: ``` rule can-be-built ( ... ) { import ../../config/checks/config : requires ; return [ requires ... ] ; } boost-install boost_<library> : @can-be-built ; ``` It would be perfect if the library could provide a meaningful explanation why it could not be built/describe not satisfied requirements, but that obviously requires a way more sophisticated system. > This is not a Mailman problem, this is a problem with how you are > replying or your mail client setup. Other users with gmail seem to not > have reply problems so I suspect it is not a gmail specific issue. A > quick look reveals that at least one concern is that your headers lack > the "in reply to". I am subscribed to the daily digest, I cannot reply to a message because I do not receive emails even if someone replied to my message or posted something to a thread I interested to be updated more frequently. > As a side-note: there are non-trivial issues with upgrading to mailman > v3; however, hopefully we will be able to upgrade things in the > not-to-far-off future. Thanks for working on that.

1 0

Regression tests not updating
by Joaquin M López Muñoz 27 Aug '21

27 Aug '21

Hi, just a heads up that regression tests are not updating since Aug 12: https://www.boost.org/development/tests/develop/developer/summary.html https://www.boost.org/development/tests/master/developer/summary.html Thank you, Joaquín M López Muñoz

3 3

Re: [boost] Unconditional conditional building is cursed"
by Nikita Kniazev 27 Aug '21

27 Aug '21

> But the problem has nothing to do with silently not building libraries. It's > caused by libraries assuming that Boost.Config is at ../config. Both have the same root cause -- no way to turn off these build checks. If the checks are not needed there is no need to import Boost.Config and assume its location too. P.S. I do not understand how to reply in the Boost mailing lists, please do not blame me if the message went to the wrong thread, I expressed my frustration about that previously, Boost needs to upgrade its Mailman to v3.

3 2

Unconditional conditional building is cursed
by Nikita Kniazev 26 Aug '21

26 Aug '21

Some libraries (Context, Contract, Fiber, Json, Math, Nowide) are built conditionally and use checks from the Config library to do that (`import ../../config/checks/config : requires ;`). Apparently, it happens to be a PITA for some consumers. Vcpkg had to hack around that and update the hack every Boost release, but Boost 1.76 revealed problems in it ( https://github.com/boostorg/build/issues/724) and Boost 1.77 is blocked by it (https://github.com/microsoft/vcpkg/pull/19556#issuecomment-904702798) I have a mixed feeling about silently not building libraries. I understand that for a lot of people it is reasonable that the default stage build will not build a library on an unsupported compiler. However, it is absolutely bad and a confusing thing to a user that the input is silently ignored when a library is requested using the `--with-<library>` flag. A way to turn off the conditional building of the libraries could also be in debug purposes alongside fixing `--with-<library>` behaviour and making possible for vcpkg to live without resorting to hacking the boost build system. I have no affiliation to vcpkg and I am not a maintainer of any mentioned libraries. It is purely my observation about how Boost is used.

2 1

Does boost have an assert that works nicely with constexpr evaluation, and if not should we add one?
by Ivan Matek 25 Aug '21

25 Aug '21

As you may know assert does not play nicely with constexpr evaluation. But std::is_constant_evaluated/if consteval gives us a way to check when the execution happens. https://www.godbolt.org/z/dfder8h16 Does something like this exist in boost, and if not would that be a nice addition? I can not figure out how to support line numbers, filename in a same way assert does, since assert will obviously just take the line info from where it is called. P.S. smart_assert is just a first name I thought of, I am fine with any name as long as it is not some lengthy monstrosity like is_constant_evaluated

4 7

Need cancel() on async_resolve() to callback the resolve handler immediately
by sandeep m.v 25 Aug '21

25 Aug '21

Hi All, I'm looking for a solution for below problem. We're using async_resolve() to perform DNS resolution using boost::asio::ip::tcp::resolver. In few instances probably during network connectivity issues, async_resolve is taking more time. When our application timeouts in 15seconds while waiting for DNS resolution, cancel() is called on resolver. But, that doesn't callback to resolve handle immediately. When I tried to search for this, it looks like, when a cancel() is called on resolver, that doesn't cancel ongoing actual resolution but may cancel if there are any other pending asynchronous action. It's taking 40seconds at times to call resolve handler even when failed to resolve host and even after calling cancel on it. My application waits until resolve handler is called after cancel() to proceed further processing. Is it possible to stop that async_resolve() and get callback to resolve handle immediately after cancel()? If that's impossible, is there a way that we can stop that doesn't callback resolve handler later? Is it possible to close underlying socket related to async_resolve from my application? Thank you in advance. Regards, Sandeep

4 8

BOOST_IS_CONSTANT_EVALUATED_INT(integer-expression)(integer-expression)
by Robert Ramey 24 Aug '21

24 Aug '21

A couple of questions regarding the above new boost config macro. a) I note that this "breaks the pattern" of BOOST_NO_... which I was expecting. I've got no complaint about this, just like being consistent when possible. b) My intended usage is something like: template<typename T> constexpr interval<T> get_interval(const & T t){ return BOOST_IS_CONSTANT_EVALUATED_INT(t) ? interval<T>(t, t) : interval<T>( std::numeric_limits<T>::min(), std::numeric_limits<T>::max() ); } is this the intended way to use this? If not, what would be the correct usage. c) In my Jamfiles I generally have a few tests which run conditionally on the config macro values like this: test-bsl-run_files test_array : A : : requires cxx11_hdr_array ; #BOOST_NO_CXX11_HDR_ARRAY What should I use with the above macro? Particularly confusing is the usage of _NO_ in the macro and the exclusion of _no_ in the requires variable. Should it be something like this. test test_is_constant_evaluted : A : : requires cxx20_no_is_constant_evaluated_int ; #BOOST_IS_CONSTANT_EVALUATED_INT d) Looks like part of this already checked into config.hpp on the develop branch. I would like to add something to my current develop to permit me to start using this now until you get the final code checked in. Any suggestions about the easiest way to do this? I'm ok with inserting some code temporarily but would prefer not to have to sprinkle it all over the place. Robert Ramey

3 8

Strange b2 headers problem
by Edward Diener 24 Aug '21

24 Aug '21

I switched my main boost repository from the 'develop' branch to an earlier tagged boost release to try something out in that earlier release. Everything went fine with switching the main repository and all submodules. I wiped out all the header links from the boost subdirectory and I tried b2 headers, only to get: error: Cannot create link boost\property_map\parallel\basic_reduce.hpp to libs\property_map_parallel\include\boost\property_map\parallel\basic_reduce.hpp. error: Link previously defined to another file, libs\property_map\include\boost\property_map\parallel\basic_reduce.hpp. This makes no sense since there is a completely empty boost subdirectory under my main boost repository directory. How do I fix this problem ?

2 3

[release]Boost 1.77.0
by Marshall Clow 22 Aug '21

22 Aug '21

Release 1.77.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraries and numerous enhancements and bug fixes for existing libraries. * Describe: A C++14 reflection library, from Peter Dimov. Provides macros for describing enumerators and struct/class members, and primitives for querying this information. * Lambda2: A C++14, dependency-free, single header lambda library, from Peter Dimov. For details, including download links, see <http://www.boost.org/users/news/version_1.77.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.77.0/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Marshall Clow, Michael Caisse, Glen Fernandes

4 7

Discuss: Editorial Control Over Repositories and Libraries
by Vinnie Falco 21 Aug '21

21 Aug '21

So, I have a whole bunch of new libraries marching towards completion and proposal for Boost. I have Boost.URL and Boost.HTTP-Proto in the works, and there is some code that I want to share between the two. Files like these: Algorithms to assist processing RFC7230 compliant input: <https://github.com/vinniefalco/http_proto/blob/9d3144c60b3426509b45cc63dbb3…> <https://github.com/vinniefalco/http_proto/blob/9d3144c60b3426509b45cc63dbb3…> <https://github.com/vinniefalco/http_proto/blob/9d3144c60b3426509b45cc63dbb3…> These are public interfaces, and they are equally useful to both URL and HTTP-Proto. They will also be likely useful to processing websocket handshake field values. It would be nice if I could put them in a separate repository with its own tests, documentation, and CI. But I don't know that this is enough meat on the bone so to speak, to justify as a complete new Boost library offering. When Boost.URL returns a std:::string the user has the option of providing a custom allocator. The library comes with this interface which uses a local stack buffer: <https://github.com/CPPAlliance/url/blob/111b83cc4726f3144194dc3546e096d60ac…> This can be used to avoid dynamic allocation when, for example - you want to apply decoding to a URL-encoded input, which happens often. Boost.HTTP-Proto would benefit from this class as well. Again we have the case of a common component that belongs in a separate repository. But this allocator isn't really related to the BNF-processing utilities mentioned above. So where would it go? As I use MSVC exclusively for regular development, I have put together a small unit test facility which is tailored to my workflow: <https://github.com/vinniefalco/http_proto/blob/9d3144c60b3426509b45cc63dbb3…> This has the flavor of Boost lightweight test, but also: * Redirects output to the Visual Studio IDE if a debugger is attached * Supports the model where one executable is built which holds all the tests * A command-line argument facility to specify individual test suites to run I use this in all of my Boost libraries and to-be-proposed libraries. I wouldn't say that it is user-facing. Currently I put a copy of the file in each library but I have made some changes and it would be better if I could put it in a shared place in the Boost tree. But it isn't public so it shouldn't be grouped with the BNF and the allocator stuff above. I am working on new libraries which do ASIO networking, and they use this handy mocking class which is used for testing stream algorithms: <https://github.com/boostorg/beast/blob/21cd552399aa8167ed53c21a74f3711c2c31…> This is a public interface, which users deploy for their own tests (for example the windows-tls project uses it). Again the case where I want to use it in tests for my own new libraries but without making a copy of the source. In other words in its own shared place. It does require ASIO, so I'm not sure it should be grouped with the rest of the stuff above. Now going back to these new libraries, I have Boost.HTTP-Proto which is a brand new library that speaks HTTP/1 but you have to bring your own networking. It is purely a low-level protocol library, but with a scope expanded from Beast to support more useful things that users need. Since networking is obviously needed I am developing the companion library Boost.HTTP-IO in parallel which uses ASIO to drive the protocol library. They use separate repositories and thus the protocol library is physically isolated, has its own tests, CI, and documentation, and so forth. There is a cosmetic issue where users have to write boost::http_proto::request if they want to declare a request container but then they have to write boost::http_io::write if they want to send the request over a socket (note the different namespaces). This is kind of annoying, and becomes even more annoying when you have to remember which namespace the error constant is located in: http_proto::error::end_of_message or http_io::error::end_of_file. One possibility is for these libraries to use the same namespace: boost::http. Or boost::http_proto. But this breaks the rule of one-repository, one-unique-namespace. Once these libraries are done I will at some point want to write Boost.Websocket-Proto and Boost.Websocket-IO which are similar to their HTTP counterparts (*). And then we will have twice the number of namespaces and error constant enums: boost::http_proto boost::http_io boost::websocket_proto boost::websocket_io and boost::urls These all have their own error enums called "error". If we create a separate repository for common code that all 5 of these libraries use, then that's a sixth namespace also with error code. Okay so that's the stuff that I've been pondering as I write this new code, are any of these real problems? What can I do about it? I'm interested in your thoughts. * The purpose of writing these new, seemingly duplicative libraries is to build on the experience of Beast to smooth out the discovered rough edges and provide a superior interface and implementation. -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

1 0