- Boost - lists.boost.org

Does anyone use mp11 with VS2013?
by Peter Dimov 11 Mar '21

11 Mar '21

Does anyone here use mp11 with Visual Studio 2013? (msvc-12.0) 2013 kind of supports C++11 but only barely, and I keep bumping into its bugs and limitations, so I'm considering dropping it and making 2015 the minimum requirement.

1 0

[Boost] [Describe] library submission - last call for reviews from the community
by Richard Hodges 11 Mar '21

11 Mar '21

A friendly reminder that the review period for [Boost.Describe] will finish at the end of tomorrow - 10th March 2021 We've had some excellent feedback already, and would value more. If you can spare a few hours of your valuable time, please consider reviewing this neat little library and posing your results on this mailing list. The invitation is repeated below: The Boost formal review of the Describe starts Monday, taking place from March 1st, 2021 to March 10th, 2021 (inclusive). The library is authored by Peter Dimov. Documentation: https://pdimov.github.io/describe/doc/html/describe.html Source: https://github.com/pdimov/describe The library provides a simple means of providing reflection for structures and enums in C++. The documentation contains a number of common motivating examples, including: - A universal print function https://pdimov.github.io/describe/doc/html/describe.html#example_print_func… - JSON serialisation https://pdimov.github.io/describe/doc/html/describe.html#example_to_json Please provide in your review information you think is valuable to understand your choice to ACCEPT or REJECT including Describe as a Boost library. Please be explicit about your decision (ACCEPT or REJECT). Some other questions you might want to consider answering: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found at: http://www.boost.org/community/reviews.html The review is open to anyone who is prepared to put in the work of evaluating and reviewing the library. Prior experience in contributing to Boost reviews is not a requirement. Thank you for your efforts in the Boost community. They are very much appreciated. Richard Hodges - review manager of the proposed Boost.Describe library Peter is often available in the CppLang Slack #boost channel should you require any clarification not covered by the documentation, as am I. Please submit your review to the Boost mailing list: boost(a)lists.boost.org -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

3 6

[release] Reminder about 1.75.0 release notes
by Marshall Clow 11 Mar '21

11 Mar '21

The master branch is closing on Wednesday for the 1.75.0 release. If you have information that should go into the release notes, now’s the time to add it. Create a PR against https://github.com/boostorg/website/blob/master/feed/history/boost_1_75_0.q… <https://github.com/boostorg/website/blob/master/feed/history/boost_1_75_0.q…> — Marshall

2 3

[release] Release notes for 1.76.0
by Marshall Clow 11 Mar '21

11 Mar '21

If you have information that should go into the release notes, now’s a good time to add it. Create a PR against https://github.com/boostorg/website/blob/master/feed/history/boost_1_76_0.q… — Marshall

1 0

[Geometry] Proposing a project idea for GSOC 2021
by Siddharth Kumar 11 Mar '21

11 Mar '21

Hey, This is Siddharth Kumar. I have been working on the Boost.Geometry library for the past 2-3 months. I would like to propose a project idea about adding features for 3d-geometries, especially polyhedral surfaces which includes:- 1. Defining a geometry for the polyhedral surfaces. 2. Read and write features for the polyhedral surfaces. 3. Defining functions for the properties of polyhedral surfaces like volume, surface area, etc. This implementation will help in the direct use of the geometry in such algorithms, which are not yet implemented for the 3d-geometries or don’t provide compatible results when working with 3d-shapes, as they give points as an output rather than taking a geometry. For example- The convex hull <https://github.com/boostorg/geometry/issues/683> doesn’t handle 3d geometries correctly, because there is no 3d geometry defined that can handle the result of the algorithm. I have already submitted a PR <https://github.com/boostorg/geometry/pull/789> (yet to be merged), which defines the geometry for polyhedral surfaces, and also includes wkt read and write features, I am willing to work on other properties of the polyhedral surfaces as a project for GSOC 2021. I am looking for a mentor who is willing to guide me in this project. Thanks

2 2

[Describe] Andrzej's review.
by Andrzej Krzemienski 10 Mar '21

10 Mar '21

Hi Everyone, This is my review of the Boost.Describe library. I recommend that the library should be **ACCEPTED** into Boost. The goal of the library is clearly specified, and addresses real world needs. The examples (JSON serialization, printing) are convincing, and the number of reviews saying "I needed it for a while" reassure that it will be useful. The library is well designed. I mean the separation into macros declaring the "reflection lsts", and then functions operating on those lists. The documentation, in connection with the clear design, makes it easy to learn and use the library. The only issues I had was with the modifiers enum: I had to look into the implementation to understand how some values work. Regarding the implementation, I only had a superficial look. One thing I observed is that the implementation is very short! When I tried to combine all headers into one, in order to test it on WandBox, I discovered that it is less than 600 lines. You can see it here: https://wandbox.org/permlink/rkAtPCbAsqNzVRMV The only issue I have is the names that start with the underscore that can potentially end up in the global namespace, which by my reading of the C++ Standard is UB. I have spent a couple of hours testing toy examples, reading the docs, and looking at the implementation. I used GCC 9.2.0 on MinGW and GCC 10.1.0 on WandBox. All worked fine. Regarding my previous concerns about the "N+1" problem (an overlap with other libraries), I no longer have it. Boost.Describe is for class and enum authors to offer a reflection information for whoever wants it. A library like Boost.Fusion is for working with fusion sequences. Only as convenience, it provides a way to adapt a user defined class as a fusion sequence, but if it wants, it can use Boost.Describe lists as an alternative way of providing the adaptation. My two real-life use cases for a reflection like this was: 1. Adapting aggregates for Boost.Spirit. It looks like even Boost.FPR would do. 2. Printing and implementing swap() and hash() for my types. So far I had to do it manually, so I am looking forward to having this library in Boost. Finally, I would like to thank Peter for writing and sharing this library. Regards, &rzej;

1 0

Boost accepted in Google Summer of Code 2021
by David Bellot 10 Mar '21

10 Mar '21

We're in again! https://github.com/boostorg/wiki/wiki/Google-Summer-of-Code%3A-2021 David

2 1

[Boost] [Describe] Review Reminder
by Richard Hodges 10 Mar '21

10 Mar '21

A friendly reminder that the review period for [Boost.Describe] is half way through. We've had some excellent feedback already, and would value more. If you can spare a few hours of your valuable time, please consider reviewing this neat little library and posing your results on this mailing list. The invitation is repeated below: The Boost formal review of the Describe starts Monday, taking place from March 1st, 2021 to March 10th, 2021 (inclusive). The library is authored by Peter Dimov. Documentation: https://pdimov.github.io/describe/doc/html/describe.html Source: https://github.com/pdimov/describe The library provides a simple means of providing reflection for structures and enums in C++. The documentation contains a number of common motivating examples, including: - A universal print function https://pdimov.github.io/describe/doc/html/describe.html#example_print_func… - JSON serialisation https://pdimov.github.io/describe/doc/html/describe.html#example_to_json Please provide in your review information you think is valuable to understand your choice to ACCEPT or REJECT including Describe as a Boost library. Please be explicit about your decision (ACCEPT or REJECT). Some other questions you might want to consider answering: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found at: http://www.boost.org/community/reviews.html The review is open to anyone who is prepared to put in the work of evaluating and reviewing the library. Prior experience in contributing to Boost reviews is not a requirement. Thank you for your efforts in the Boost community. They are very much appreciated. Richard Hodges - review manager of the proposed Boost.Describe library Peter is often available in the CppLang Slack #boost channel should you require any clarification not covered by the documentation, as am I. -- Richard Hodges hodges.r(a)gmail.com office: +442032898513 home: +376841522 mobile: +376380212

6 5

[Describe] Review - Part 1: Enumerators
by Andrzej Krzemienski 10 Mar '21

10 Mar '21

Hi Everyone, This is part one of my review of Boost.Describe. I will focus only on dealing with enumerators. Working with C++ enumerations is harder than one might think, because they are not what many people believe. They are just a bunch of integral constants and an integral type. We can get things like this: enum Season { Spring = 1, Summer, Autumn, // British Fall = Autumn, // American Winter, }; struct Human { std::string name; Season born; }; int main() { Human h {}; inspect(h); } void inspect(Human h) { switch(h) { case Spring: case Summer: case Fall: case Winter: return; default: assert(false) } } I can trigger an assertion failure without even doing any cast, because enums can assume other values that those listed in the declaration. The low-level interface provided by Boost.Describe is able to manage all these aspects very nicely. If we call BOOST_DESCRIBE_ENUM on struct Season above, we will get a list of five elements and the user will have to decide what she wants to do with it. On the other hand, requesting that Boost.Describe should provide a higher level enum-to-string mapping seems to overlook the special rules of C++ enums. How do you want this function to behave if the input enum value is not found? What do you want the function to do if it finds more than one corresponding string? The interface of describe_enumerators<> is optimal. Macro BOOST_DESCRIBE_ENUM is redundant: BOOST_DESCRIBE_ENUM_CLASS can handle unscoped enumerations pretty well. Note that in C++11 you can use the qualified names of unscoped enumerators, like Season::Winter in the above example. After playing first with macros for describing structs, I was surprised that the syntax for describing enumerators doesn't use parentheses for the list of enumerators: BOOST_DESCRIBE_ENUM(X, (A, B, C)); // I somehow expected that to work. Describing enums from the global namespace introduces names starting with underscore (_enum_descriptor_fn) into global namespace. This is Undefined Behavior, and is likely to trigger some code sanitizers. Instead use an ugly name, like boost_describe_enum_descriptor_fn. I do not appreciate the BOOST_DEFINE_ macros for enumerations. We get as much as four of them, and neither is able to handle the use case that I consider basic, which I often have in my code: where I omit value zero and start from 1: struct Error { badSoething = 1, badSomethingElse, tooLongSomethng, ... }; So, I am not sure how many real life enums these macros cover. Regards, &rzej;

3 4

[release] Reminder: Master branch closing WEDNESDAY 3/10 for 1.76.0 beta release
by Marshall Clow 10 Mar '21

10 Mar '21

Calendar here: https://www.boost.org/development/ <https://www.boost.org/development/> — Marshall

2 1