- Boost-users - lists.boost.org

Fwd: [GSoC 2020][GIL] Mentors and project proposals
by Mateusz Loskot 17 Jan '20

17 Jan '20

FYI, https://lists.boost.org/boost-gil/2020/01/0372.php, copied below. ---------- Forwarded message --------- From: Mateusz Loskot <mateusz(a)loskot.net> Date: Fri, 17 Jan 2020 at 23:17 Subject: [GSoC 2020] Mentors and project proposals To: <boost-gil(a)lists.boost.org> Dear All, I have started collecting proposals of GIL projects for GSoC 2020. On the Boost official GSoC 2020 wiki, I've added Image Processing project as continuation of Miral's project from 2019: https://github.com/boostorg/boost/wiki/Google-Summer-of-Code:-2020 If Boost will participate, I should be able to mentor this year. Stefan, are you on board too? Who else? If there are students and mentors interested in GIL, it is time to stop being shy ;) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[Graph] Large incoming changes to Boost.Graph master.
by John Maddock 08 Jan '20

08 Jan '20

Dear all, Boost.Graph has had no maintainer for some time, but the CMT has been busy fixing bugs none the less. Unfortunately, other than some trivial fixes to docs and some directory refactoring, nothing much has been merged to master in a good while . On the plus side, develop is now in a better tested tested state than IMO it has ever been, however the change set is rather large so the potential to mess up somebodies code is certainly there: https://github.com/boostorg/graph/pull/196. So... this is both a heads up, and a plea: if you have any mission critical code using the Graph library, could you please test against current develop and report any problems? If you don't want to mess about with git, download from https://github.com/boostorg/graph/archive/develop.zip and place zipfile-contents/libs/graph/include in your include path ahead of that for Boost-1.72. Many thanks, John.

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Matt Calabrese 07 Jan '20

07 Jan '20

On Sat, Jan 4, 2020, 20:23 Ronald Garcia via Boost <boost(a)lists.boost.org> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > Thanks for everything, Ron! >

1 0

Re: [Boost-users] [boost-steering] Retirement as Review Wizard
by Antony Polukhin 06 Jan '20

06 Jan '20

Many thanks for all your contributions! On Sat, Jan 4, 2020, 22:03 Ronald Garcia <rxg(a)cs.ubc.ca> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > > > Sincerely, > Ron Garcia > Boost Co-Review Wizard > > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google Groups > "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to boost-steering+unsubscribe(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/BFFCD488-2E57-4161-8D13-2D… > . >

1 0

Re: [Boost-users] [boost-steering] Retirement as Review Wizard
by Jon Kalb 06 Jan '20

06 Jan '20

Ron, For myself and on behalf of the Boost Steering Committee, thanks very much for both your effort on behalf of the Boost community and the leadership that you've demonstrated. Jon On Sat, Jan 4, 2020 at 2:03 PM Ronald Garcia <rxg(a)cs.ubc.ca> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > > > Sincerely, > Ron Garcia > Boost Co-Review Wizard > > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google Groups > "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to boost-steering+unsubscribe(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/BFFCD488-2E57-4161-8D13-2D… > . >

1 0

[Geometry] Trouble with adapting geometric objects to Eigen to use convex_hull on multiple polygons
by Rostyslav-Paul Wilhelm 06 Jan '20

06 Jan '20

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Glen Fernandes 05 Jan '20

05 Jan '20

On Ronald Garcia wrote: > > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time has come for me to step down from the position, and make room for a new face with fresh ideas. It has been my pleasure to serve in this position for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! Many thanks for your service to Boost all these years, Ron. Glen

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Niall Douglas 05 Jan '20

05 Jan '20

On 04/01/2020 19:02, Ronald Garcia via Boost wrote: > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time has come for me to step down from the position, and make room for a new face with fresh ideas. It has been my pleasure to serve in this position for this time alongside first Tom Brinkman and now John Phillips. Many Boost folk may not be aware, but Ron does a ton of stuff behind the scenes which no one publicly notices. I can think of at least two occasions during my time within Boost innards where Ron stepped in to defuse a problem, or found a solution which wasn't apparently possible. Boost will be the less for Ron's departure. Thank you for your service, and best of luck in your future endeavours! Niall

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Vinnie Falco 05 Jan '20

05 Jan '20

On Sat, Jan 4, 2020 at 5:23 PM Ronald Garcia via Boost <boost(a)lists.boost.org> wrote: > After roughly 14 years as a Boost Co-Review Wizard > I feel that the time has come for me to step down from the position, > and make room for a new face with fresh ideas. Thank you for your generous investment of time to act as a Boost Review Wizard! Does this mean that you are now available to act as a regular Review Manager? Because there's this library... Thanks

1 0

[review][STLInterfaces] STLInterfaces review results
by Barrett Adair 26 Dec '19

26 Dec '19

Many thanks are owed to all who participated in the formal review of Zach Laine's STLInterfaces library, especially during this busy holiday season: * Hadriel Kaplan - ACCEPT * Andreas Wass - ACCEPT * Rainer Deyke - ACCEPT * Arthur Gruzauskas - ACCEPT * Krystian Stasiowski - ACCEPT * Daniela Engert - CONDITIONALLY ACCEPT * Gavin Lambert - Technical comments First, a summary of the reviews: 1. Design Reviewers were unanimous in their appreciation for the design. Krystian had the only asterisk about the design, noting that derived class members should ideally be SFINAE-detected, where the library feature would SFINAE where the corresponding required derived feature detection fails. I have a different opinion about this, but we can discuss that elsewhere. 2. Implementation The container_interface destructor and the optional dependency on cmcstl2 were snags for multiple reviewers. Several compile errors were discovered that need to be addressed. 3. Documentation Reviewers found the documentation to be "ok". A common request was for better organization of derived-class requirements, particularly with the container_interface template. Reviewers also lamented the lack of training wheels for the subject matter. 4. Tests Hadriel noted the lack of non-copyable value_type tests, while Daniela noted the lack of Boost.Build support. Hadriel was the only one who commented on the quality of tests ("good"), and the only one who ran them. Arthur did his own testing, to satisfaction. I appreciate the presence of SFINAE-friendliness tests and the continuous integration. 5. Usefulness Reviewers appreciated the usefulness of the library. Arthur is "using it happily", while others found it "very useful", "fairly useful", or of "high" usefulness. However, Krystian's response implied that this library may not be as useful for containers needing extreme performance. The reviews clearly demonstrate a consensus. Accordingly, I'm pleased to announce that STLInterfaces is CONDITIONALLY ACCEPTED as a Boost library. Conditions for acceptance: 1. Remove optional dependency on cmcstl2 (issue #27) 2. Add Boost license comments to all files, including appveyor.yml, .travis.yml, README.md, */CMakeLists.txt (issue #26) 3. Support Boost.Build (issue #25) 4. Replace googletest with Boost equivalent (issue #24) 5. Remove usage of non-existent v2_dtl members in container_interface.hpp (issue #22) 6. Include <tuple> for std::tie usage in C++14 mode (issue #21) 7. Fix dangling parens in container_inteface.hpp:731 (issue #20) 8. Make Concepts usage C++20-conformant (issue #13) 9. Remove the destructor in container_interface (issue #12) 10. Add tests for non-copyable value types (issue #30) Suggestions: 1. Explicitly document the signatures and return types of functions provided by base class templates (issue #23) 2. Mention the C++20 generator pattern in documentation (issue #19) 3. Document the library's interactions with Ranges (issue #18) 4. Remove unnecessary comments (issue #17) 5. Investigate compile error in VS2015 (msvc 19.0.3) due to issues with noexcept() operator in function overloading (issue #16) 6. Rename container_interface to sequence_container_interface (issue #15) 7. Change the 'contiguous' bool to an enum (issue #14) 8. Document the relationship between value_type operator== and containter_interface-defined operator== (issue #11) 9. Improve table/section names for better navigation of container_interface tutorial (issue #10) 10. Clean up BOOST_STL_INTERFACES_DOXYGEN usage (issue #28) 11. Split up fwd.hpp into multiple headers (issue #29) 12. Document optimization trade-offs of proxy_iterator_interface (issue #30) Rationale: 1. Condition #1 is, I feel, the appropriate default as review manager. If Zach feels strongly about keeping the optional dependency on cmcstl2, we should discuss. 2. Unless the library requirements webpage has fallen out of date, new libraries must still support Boost.Build. 3. A not-so-quick grep of current Boost libraries yields no `gtest` results. I assume that we do not allow googletest as the sole test framework in a library. 4. The other conditions should be self-explanatory. Thank you Zach for your contributions, and I look forward to working with you to add this library into Boost. Regards, Barrett Adair

1 0