- Boost - lists.preview.boost.org

[variant2] request to extend the review period
by Andrzej Krzemienski 08 Apr '19

08 Apr '19

Michael, Peter, Would it be possible to extend the review period? I may only be able to devote more time to the review on Thursday, so if it was possible to extend the review at least till 12th, I might have a chance to get it done. I suspect, I might be not the only one in this situation. Regards, &rzej;

1 0

Re: [boost] variant - off topic
by Bjorn Reese 08 Apr '19

08 Apr '19

On 4/3/19 11:27 PM, Robert Ramey via Boost wrote: > d) insert your own use case here. That is, look at your own usages of > assignment to these types and see if there is not an easy way to > re-factor your code to avoid assignment. Such refactoring is difficult for state machines where you use a variant to denote the current state.

4 9

Enabling spectre mitigation in boost libraries
by Riff J 08 Apr '19

08 Apr '19

Hi everyone, I am a developer from Microsoft and currently using boost in our project. We recently get noticed by our security team, that the boost library we use, are not compiled with spectre mitigation (/Qspectre) enabled. Since boost is super powerful, it might not be a good idea to write our own or maintain our own version, so we are reaching out for help. Could anyone please help see if we could enable /Qspectre option in the official build of boost? And here is the vcblog about the spectre mitigation, if anyone is interested: https://blogs.msdn.microsoft.com/vcblog/2018/01/15/spectre-mitigations-in-m… . And since this is the first time I use this mail list, please let me know, if I didn't use it correctly or anything I should pay attention to. Thanks a lot, Riff

10 22

[gsoc19] Boost.Geometry Delaunay triangulation and Voronoi diagrams
by Georgios Venizelos 08 Apr '19

08 Apr '19

Hello, I would like to undertake the Delaunay/Voronoi project in Boost.Geometry library. I have already shared my proposal on GSoC through Google Docs. I think that Delaunay triangulation is a process that has many applications, so it is useful to have such a process implemented in Boost libraries. Main focus of the program would be to implement Delaunay and Voronoi for Cartesian coordinates in 2 and 3 dimensions. If finished early, this could extend either in higher dimensions or in other coordinate types. Would anyone be interested in mentoring such a GSoC project? With respect, Georgios Venizelos --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

Re: [boost] Enabling spectre mitigation in boost libraries
by Kenneth Porter 08 Apr '19

08 Apr '19

On 4/6/2019 9:46 AM, John Maddock via Boost wrote: > One thing we could look at for future releases would be to provide > differently-named binaries for /Qspectre. Anyone else have thoughts > on that? I just looked at the libraries available via the Visual Studio installer and I see this in my installation (using atls as an example MS-supplied library): C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.20.27508\atlmfc\lib\spectre\x64\atls.lib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.20.27508\atlmfc\lib\spectre\x86\atls.lib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.20.27508\atlmfc\lib\x64\atls.lib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.20.27508\atlmfc\lib\x86\atls.lib That may give some guidance as to how MS can package the Boost libraries for internal distribution.

1 0

Re: [boost] [variant2] Andrzej's review -- design
by Mike 08 Apr '19

08 Apr '19

> Going back to variant, in one case, we are defining an empty state, which > forces the user to provide explicit handling for that state, *everywhere*. You keep repeating that the user would have to explicitly handle that everywhere. I thought I just showed you that this is not the case. Except for visit, you don't have to explicitly handle the valueless state at all and even in the case of visit, you might be fine with std::visit just throwing an exception, because that is indeed an exceptional circumstance. I don't see this *everywhere* at all. Best Mike

8 18

[release] Master branch now completely closed for the 1.70.0 release
by Marshall Clow 08 Apr '19

08 Apr '19

The master branch is now closed for all changes except by permission for the release. Also, remember to add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_70_0.q… > Thanks, -- The Boost Release Team

4 7

Regarding Boost.Astronomy GSoC19 proposal review
by sarthak2007 07 Apr '19

07 Apr '19

Hello community, I am Sarthak Singhal, pursuing B.Tech in Computer Science from Indian Institute of Technology, Kanpur. I had submitted the programming competency test to mentor and also got a positive response from her. I had also submitted the project proposal to the mentor and based on her suggestions have improved it also. I have submitted the draft of the proposal to GSoC site. I request you to go through the proposal. I will appreciate your feedback to improve the proposal. Thank you, Sarthak Singhal -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

2 4

[release] Boost 1.70.0 Release Candidate 1 available
by Marshall Clow 07 Apr '19

07 Apr '19

The release candidates for the 1.70.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.70.0/source/> The SHA256 checksums are as follows: 6e5cba1269225395bb5e78dda48441ccadaf745e42638180015e9e6257068336 ./boost_1_70_0_rc1.7z 35d8e1361e2063f70aa3a6ca0dd8af0877ceb75477ebbd2c726bb1d039658c7a ./boost_1_70_0_rc1.tar.bz2 ec8ddbbee2fd61e2f78a1dfe9a07ad83ca8f6a2f4c704d6f297d89c6afdc4f2c ./boost_1_70_0_rc1.tar.gz ee2c3b97ce10f85a31b6a105ad8edf1c20fb4b936c9a6e6008206059cb98ab1b ./boost_1_70_0_rc1.zip 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 Boost Release Managers

7 14

Re: [boost] [Boost-users] [release] Boost 1.70.0 Release Candidate 1 available
by Marshall Clow 07 Apr '19

07 Apr '19

On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users < boost-users(a)lists.boost.org> wrote: > On 04.04.19 16:27, Marshall Clow via Boost-users wrote: > > 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. > > boost::movelib::adaptive_merge continues to be broken if > iterator_traits<RandIt>::size_type != std::size_t. This breaks > boost::container::flat_map when cross-compiling for MacOS. I have > previously reported this error here. > > I consider this a critical error - as in, I won't be able to upgrade to > Boost 1.70 at all unless this error is fixed for the release. > This is https://github.com/boostorg/move/issues/25, correct? -- Marshall

1 0