March 2020 - Boost - lists.preview.boost.org

Regarding PCT (boost astronomy , coordinate transformation/conversion)
by GOPAL RAMESH DAHALE 28 Mar '20

28 Mar '20

I have written a class to transform cartesian_representation vector with the help of the affine matrix(3x3). My problem is that I am not able to work with boost::unit:: quantity. I work with the quantity values but later on not able to assign it to the resulting cartesian_represtentaion(res). Any help is appreciated. Thank You.

2 1

[boost.multiprecision] Request to review GsoC proposal.
by Abhay Yadav 28 Mar '20

28 Mar '20

Hello, I have prepared the GsoC proposal. Please provide your valuable feedback. Proposal link : https://docs.google.com/document/d/1j9avtkQALwnesyKAq40wFtPaA1Adp2RUf3FUGCP… Thank you Regards, Abhay Singh Yadav

1 0

Fwd: new toolset in b2
by Grzegorz Konopko 28 Mar '20

28 Mar '20

Dear I am thinking about make automatic test for boost, but with not supporting toolset yet. Is there any tutorial or template for b2: how to add new toolset support? I was looking documentation already, in my opinion no simply way due lack of kind of "easy tutorial". Best regards Grzegorz Konopko

1 0

Hiring mentors for Google Summer of Code 2020
by David Bellot 28 Mar '20

28 Mar '20

Hi Boost community, we are recruiting the mentors for the Google Summer of Code 2020. If you wish to be a mentor, please contact me directly and I'll send you an invite. We need at least 10 mentors this year. Obviously, a mentor comes with ideas of projects and proposals for this Summer. Best regards, David

8 10

Looking for Boost.uBlas data frames project GSoC mentors
by Tom Kwok 28 Mar '20

28 Mar '20

Hi everyone, May I know if there are any potential mentors for my Boost.uBlas data frames project proposal besides Mr. David Bellot? He has not been responding to messages lately. Not sure if it is because of the recent Covid-19 situation. Best regards, Tom

6 12

[geometry] Global Boost documentation for master not refreshed?
by Mateusz Loskot 27 Mar '20

27 Mar '20

Hi, A long while ago there was a problem in Boost.Geometry [1] that caused addition of unwanted sections to the global docs: https://www.boost.org/doc/libs/1_70_0/#lib-geometry-extensions https://www.boost.org/doc/libs/1_70_0/#lib-geometry-index and the problem [1] has been fixed a while ago in the Geometry, in both branches develop and master. [1] https://github.com/boostorg/geometry/issues/585 The global docs for the develop branch look fixed, no unwanted sections, just the one we want: https://www.boost.org/doc/libs/develop#lib-geometry The global docs for the master branch still lists one of the two unwanted sections https://www.boost.org/doc/libs/master#lib-geometry-extensions Why is that? Are we still waiting for the rebuild or something had not cleaned up correctly before the last rebuild? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

Boost Astronomy gsoc
by GOPAL RAMESH DAHALE 27 Mar '20

27 Mar '20

I want to contribute to boost astronomy in gosc and I have read that I have to find a mentor who is an experienced boost developer and then write the proposal. What should I do? I am not able to understand the procedure for contributing to boost. Please help. I appreciate that. Thank you.

2 1

uBlas and Google Summer of Code 2020
by David Bellot 27 Mar '20

27 Mar '20

Hi Boost community, I've added new projects for the Google Summer of Code 2020 for the Boost uBlas library (matrix computations, tensors and linear algebra). If you're a student and wish to candidate, please contact me as soon as possible. The list of projects is here: https://github.com/boostorg/wiki/wiki/Google-Summer-of-Code%3A-2020 Cheers, David

4 5

[GSoC 2020] Proposal Review
by deb 27 Mar '20

27 Mar '20

Here is my proposal for GSoC 2020. It takes into account the new timeline announced today. I do not ask for a full review (which can be done after the final submission) just a glance from the potential mentors to provide feedback on any section I might have missed or needs to be modified. Link to docs - https://docs.google.com/document/d/1qZZSuTF2xQoZVnkVeahDDIMlIJ5iiSUn0BMJxo7… Thanks in advance. Debabrata Mandal -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

2 1

1.73.0 Release process has started!
by Marshall Clow 26 Mar '20

26 Mar '20

The deadline for new libraries and breaking changes has passed. Upcoming dates: 1-Apr Boost 1.73.0 closed for major changes 8-Apr Boost 1.73.0 closed for beta ASAP Boost 1.73.0 beta 22-Apr Boost 1.73.0 closed for release ASAP Boost 1.73.0 release "ASAP", in this list, means "As soon as possible after the preceding milestone" -- Marshall

1 0

[geometry] Planning switch to C++11
by Mateusz Loskot 26 Mar '20

26 Mar '20

Hi, We are planning to switch Boost.Geometry to C++11 https://github.com/boostorg/geometry/issues/590 Is the following procedure sensible: 1. Warn users on the Boost mailing lists about the planned switch to C++11 2. Make the switch (update the codebase) 3. Release the Boost.Geometry as C++11 e.g. with Boost 1.75 4. Announce on the Boost mailing lists that Boost.Geometry requires C++11 Are there any recommendations or requirements on how we should proceed? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

7 16

[GSoC 2020] Proposal Review for Boost.Multiprecision
by aman mahansaria 26 Mar '20

26 Mar '20

Hello Boost Team, I have prepared my draft proposal for Boost.Multiprecision project on Extending and optimizing the library for thousands of bits. The link for the same is: https://docs.google.com/document/d/1BgDtR2VCoxq0FFPCyK50l6crG9GMrTKkDYDCRoi… Please kindly provide your valuable feedback on the same. I had also submitted the same for review on the GSoC site as well. Let me know in case there is any issue with viewing of the document. Thanks and Regards, Aman Mahansaria First Year M.Tech CSE, NIT Trichy

2 1

[GSoC 2020] Proposal Review for Boost.Multiprecision
by Ram Nad 26 Mar '20

26 Mar '20

Hello Everyone, I have prepared my draft proposal for Boost.Multiprecision project on Extending and optimizing the library for thousands of bits. Here is the link, https://docs.google.com/document/d/1C0GkLYGuBjLvIdp-NvGJAjxwtUvY7xfNGxOlaOW… I have been in touch with the potential mentors of this project for quite some time now. This proposal is result of my discussions with them. Please kindly provide your valuable feedback on the same. P.S. I have also submitted the same for review on the GSoC site as well. Also, please let me know if there are some visibility issues or comment access is not working. Thank you Ram Nad Second Year CSE Undergraduate Indian Institute of Information Technology, Sri City

2 2

[gsoc20] Proposal review for extending Boost.Multiprecision to higher precision
by dim131 26 Mar '20

26 Mar '20

Hi Boost community, I have prepared a draft of my proposal for extending and optimising Boost.Multiprecision to higher precision, after an initial discussion with Christopher Kormanyos: https://docs.google.com/document/d/100he6gJnUCilhsEiRWaL7PYi0IZaAL4tJfu-D3y… Any feedback will be greatly appreciated. Thank you, Dim131 -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

3 3

[lightweight_test] cpp_main convention
by Mateusz Loskot 25 Mar '20

25 Mar '20

Hi, I noticed this as popular convention across Boost libraries (e.g. endian) to deal with test cases that may throw or leak exceptions: int cpp_main( int argc, char* argv[] ) { test(); return ::boost::report_errors(); } int main( int argc, char* argv[] ) { try { return cpp_main( argc, argv ); } catch( std::exception const & x ) { BOOST_ERROR( x.what() ); return boost::report_errors(); } } Is there any reason to prefer that one over this one? int main( int argc, char* argv[] ) { try { test(); } catch( std::exception const & x ) { BOOST_ERROR( x.what() ); } return boost::report_errors(); } Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2

Preliminary release schedule for 1.73.0
by Marshall Clow 25 Mar '20

25 Mar '20

We missed the start of the release cycle for 1.73.0. Bad release managers. No biscuit. Here's my preliminary schedule for the 1.73.0 release: 25-Mar Boost 1.73.0 closed for new libraries and breaking changes 1-Apr Boost 1.73.0 closed for major changes 8-Apr Boost 1.73.0 closed for beta ASAP Boost 1.73.0 beta 22-Apr Boost 1.73.0 closed for release ASAP Boost 1.73.0 release "ASAP", in this list, means "As soon as possible after the preceding milestone" Please let me know if you see any problems with this. -- Marshall

2 2

Strange failure in regression matrix
by Alexander Grund 24 Mar '20

24 Mar '20

Hi, I got a failure of Boost.Nowide develop (and master) for msvc-14.0 in the regression matrix although that configuration is tested as far as I can tell. Furthermore there isn't any indication WHAT failed, see https://www.boost.org/development/tests/develop/developer/output/teeks99-09… Am I missing anything or is this a quirk of the regression tester? Thanks, Alex

1 0

Bug in Boost.Asio strand(strand<OtherExecutor>&& other)
by Niklas Gürtler 24 Mar '20

24 Mar '20

Hello, there is a bug in the Boost.Asio strand::strand(strand<OtherExecutor>&& other) move constructor as it tries to do an invalid cast on the wrong object. A friend declaration is also required to access the private members of the other strand. I submitted a PR https://github.com/boostorg/asio/pull/333 to address this issue. Regards, Niklas

1 0

[gsoc] Example of exceptional project proposal
by Mateusz Loskot 24 Mar '20

24 Mar '20

...as it is not Dear students, if you aim to submit proposals like this, then please don't bother polluting the GSoC space with such rubbish. Please, let's display some minimum of professionalism and respect to each other. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[GSoC 2020] Proposal Review
by Ayush Bansal 24 Mar '20

24 Mar '20

Hi Boost Community, I have prepared a draft of my Proposal for Boost.GIL's Project on Implementation of Image Processing Algorithms. I'd love to hear your comments on the same. Link to Proposal - https://docs.google.com/document/d/1JwHOxS6DG0c0GgvBnpSmvxz1PtgMMlrga9FJOyO… Please let me know you reviews :) Thank you and Regards Ayush Bansal Fifth Year Undergraduate Student Department of Computer Science and Engineering IIT Kharagpur LinkedIn <https://www.linkedin.com/in/ayush-bansal-b0727a116/>

4 5

[Optional] Merge to master
by Alexander Grund 24 Mar '20

24 Mar '20

Hi, can Boost.Optional be merged to master? There is even a CI failure on develop with a PR fixing this. So would be great if those could be merged shortly. Thanks

1 0

[config] Merging 'develop' to 'master' before the 1.73 release
by Edward Diener 23 Mar '20

23 Mar '20

Are the changes in config's 'develop' branch going to be merged to the 'master' branch before the 1.73 release ? The reason I ask is that a config 'develop' PR which I authored is a dependancy of the tti library, ans I can not merge the 'develop' changes of tti into 'master' unless those config changes also are merged to 'master'.

2 2

Re: [boost] Looking for Boost.uBlas data frames project GSoC mentors
by Tom Kwok 23 Mar '20

23 Mar '20

Hi CB, Thank you for your suggestions. I will continue with my proposal and start solving the competency test. David as of now still has not replied though. So I might need to request for mentorship for Boost uBlas data frame GSoC project here. Is anyone interested in offering mentorship and reviewing my proposal and questions? Best regards, Tom > On 19 Mar 2020, at 3:00 PM, boost-request(a)lists.boost.org wrote: > > Date: Wed, 18 Mar 2020 18:26:43 +0100 > From: Cem Bassoy <cem.bassoy(a)gmail.com <mailto:cem.bassoy@gmail.com>> > To: boost(a)lists.boost.org <mailto:boost@lists.boost.org> > Subject: Re: [boost] Looking for Boost.uBlas data frames project GSoC > mentors > Message-ID: > <CADrR+Fv8r8GrNFs-w_bvy2VBmDP6w0w+FOOOeDh0Rax02-gBEw(a)mail.gmail.com <mailto:CADrR+Fv8r8GrNFs-w_bvy2VBmDP6w0w+FOOOeDh0Rax02-gBEw@mail.gmail.com>> > Content-Type: text/plain; charset="UTF-8" > > Hi Tom, > > probably David will be the only mentor for the data frame project. I > suggest that you continue with your proposal and solve the competency test. > You can find the data frame code at > https://github.com/BoostGSoC19/data_frame <https://github.com/BoostGSoC19/data_frame> > > Last year I mentored two great students for the Tensor project > <https://github.com/BoostGSoC19/tensor/wiki <https://github.com/BoostGSoC19/tensor/wiki>>. This year I can only mentor > one student. > > Good luck, > CB

2 1

[GSOC] [boost.multiprecision] Regarding test cases.
by Abhay Yadav 23 Mar '20

23 Mar '20

Hello, In the project of Multiprecision Big Number Types I have completed programming competency test but I want to know how test cases for higher precision will be generated? Is there any platform where we can compare desired output with my output? It will be more helpful.for me for proceeding in this project.. Thank you Regards, Abhay Singh Yadav

3 3

[parameter][1.73] Library broken and unattended. Regressions and unmerged PR.
by Andrey Semashev 22 Mar '20

22 Mar '20

Hi, I'd like to draw attention to Boost.Parameter state. Since 1.71, it seems to be broken as described in these issues: https://github.com/boostorg/parameter/issues/91 https://github.com/boostorg/parameter/issues/97 The latter one was actually reported to me in Boost.Log, as this Boost.Parameter bug affected its users in a rather nasty way (the user's code silently compiles and has the wrong effect). For the latter issue I created a PR with a fix: https://github.com/boostorg/parameter/pull/99 which got no reply so far. The person who assumed Boost.Parameter maintenance and made the problematic changes, Cromwell D. Enage, is not responding, so the library is basically broken and unmaintained. I really don't want 1.73 to be released with a bug like the one affected Boost.Log, so I would appreciate if someone with merge permissions could merge my PR. If not, I will be forced to fork the library internally in Boost.Log for 1.73 (which I also really don't want to do). This would take care of my immediate concern. The other issue seems to be affecting users as well and I don't have the solution for it. Given that the library is unmaintained, it might be better to: 1. Move the current state of develop to a separate branch. 2. Revert master and develop to a state prior to Cromwell's commits that went into 1.71 (i.e. to the 1.70 state). This should take care of the Boost.Log issue as well, so it would be fine with me as well. Thanks.

2 2