June 2015 - Boost - lists.preview.boost.org

Re: [boost] [test] Develop branch test runners crashing
by Andrey Semashev 23 Jun '15

23 Jun '15

On Tue, Jun 23, 2015 at 4:32 PM, Tom Kent <lists(a)teeks99.com> wrote: > Sometime between 22:30 and 03:30 last night (pacific time) all the develop > tests started crashing on windows and linux. > > The tail of results/bjam.log is: > > notice: iostreams: not using bzip2 compression > notice: iostreams: not using bzip2 compression > ..\libs\test\test\Jamfile.v2:59: in docs-example-as-test > *** argument error > * rule boost.test-self-test ( test-rule : test-suite : test-name : > usage-variant ? : pattern_file * : source_files * : extra-libs ? : > extra-options ? ) > * called with: ( : ../doc/examples : : included : : > /D:/t08/run/boost_root/libs/test/doc/examples/boost_test_bitwise.run-fail.cpp > ) > * missing argument test-rule > ..\libs\test\test\Jamfile.v2:18:see definition of rule > 'boost.test-self-test' being called > (builtin): in sequence.transform > ..\libs\test\test\Jamfile.v2:162: in modules.load > D:/t08/run/boost_bb/src/build\project.jam:325: in load-jamfile > D:/t08/run/boost_bb/src/build\project.jam:64: in load > D:/t08/run/boost_bb/src/build\project.jam:145: in project.find > D:/t08/run/boost_bb/src/build\targets.jam:452: in find-really > D:/t08/run/boost_bb/src/build\targets.jam:474: in find > D:/t08/run/boost_bb/src/build\targets.jam:305: in targets-to-build > D:/t08/run/boost_bb/src/build\targets.jam:270: in > class(a)project-target.generate > D:/t08/run/boost_bb/src\build-system.jam:707: in load > D:\t08\run\boost_bb\src/kernel\modules.jam:295: in import > D:\t08\run\boost_bb\src/kernel/bootstrap.jam:139: in boost-build > D:\t08\run\boost_root\boost-build.jam:17: in module scope > > Any thoughts? Looks like a Boost.Test issue.

1 0

Develop branch test runners crashing
by Tom Kent 23 Jun '15

23 Jun '15

Sometime between 22:30 and 03:30 last night (pacific time) all the develop tests started crashing on windows and linux. The tail of results/bjam.log is: notice: iostreams: not using bzip2 compression notice: iostreams: not using bzip2 compression ..\libs\test\test\Jamfile.v2:59: in docs-example-as-test *** argument error * rule boost.test-self-test ( test-rule : test-suite : test-name : usage-variant ? : pattern_file * : source_files * : extra-libs ? : extra-options ? ) * called with: ( : ../doc/examples : : included : : /D:/t08/run/boost_root/libs/test/doc/examples/boost_test_bitwise.run-fail.cpp ) * missing argument test-rule ..\libs\test\test\Jamfile.v2:18:see definition of rule 'boost.test-self-test' being called (builtin): in sequence.transform ..\libs\test\test\Jamfile.v2:162: in modules.load D:/t08/run/boost_bb/src/build\project.jam:325: in load-jamfile D:/t08/run/boost_bb/src/build\project.jam:64: in load D:/t08/run/boost_bb/src/build\project.jam:145: in project.find D:/t08/run/boost_bb/src/build\targets.jam:452: in find-really D:/t08/run/boost_bb/src/build\targets.jam:474: in find D:/t08/run/boost_bb/src/build\targets.jam:305: in targets-to-build D:/t08/run/boost_bb/src/build\targets.jam:270: in class(a)project-target.generate D:/t08/run/boost_bb/src\build-system.jam:707: in load D:\t08\run\boost_bb\src/kernel\modules.jam:295: in import D:\t08\run\boost_bb\src/kernel/bootstrap.jam:139: in boost-build D:\t08\run\boost_root\boost-build.jam:17: in module scope Any thoughts?

1 0

[coroutine2] Difference between coroutine and coroutine2
by Aaron Levy 23 Jun '15

23 Jun '15

Are boost::coroutines::symmetric_coroutine<> and boost::coroutines::asymmetric_coroutine<> part of the coroutine library or coroutine2 library. Besides being C++14-only, in what ways does coroutine2 differ from coroutine? -- Aaron Levy aaron.levy(a)yandex.com

5 7

[Optional] Monadic bind
by Tobias Loew 23 Jun '15

23 Jun '15

While playing around with boost::optionals I had code like the following struct A { ... int i; ... }; boost::optional a; // do something with 'a' // optional-projection to a::i boost::optional<int> a_i; if(a) a_i = a->i; which seemed quite verbose for something that's rather natural in functional languages: boost::optional is a monadic structure, which lifts a type T by extending it with a new bottom-element (represented by the empty optional<T>), thus it should also have a "bind" and a "map"-equivalent, which could be implemented for instance as as member functions of optional template<class B> auto bind(B&& binder) const -> boost::optional<typename std::decay<decltype(std::bind(binder, get())())>::type> { if(this->is_initialized()) { return std::bind(binder, get())(); } else { return boost::none; } } and template<class B> auto map(B&& f) const -> boost::optional<typename std::decay<decltype(std::bind(f, get())())>::type> { if(this->is_initialized()) { return std::bind(f, get())(); } else { return boost::none; } } where map lifts f from A->B to optional -> optional< B > and applies 'this' to it. This would allow things like boost::optional a; auto a_i = a.map(&A::i); // "optional-projection"; type of a_i is boost::optional<int> Tobias -- View this message in context: http://boost.2283326.n4.nabble.com/Optional-Monadic-bind-tp4677431.html Sent from the Boost - Dev mailing list archive at Nabble.com.

2 7

[test] Where we are with the new version?
by Vicente J. Botet Escriba 23 Jun '15

23 Jun '15

Hi, I'm wondering if the new Boost.Test will be merged one day to the master branch. Best, Vicente

3 5

[config] 'requres' doesn't take differing -std into account
by Peter Dimov 22 Jun '15

22 Jun '15

I have, in my user-config.jam, using gcc ; feature.subfeature toolset gcc : std : cxx0x cxx11 cxx1y cxx14 : optional composite propagated ; feature.compose <toolset-gcc:std>cxx0x : <cxxflags>-std=c++0x ; feature.compose <toolset-gcc:std>cxx11 : <cxxflags>-std=c++11 ; feature.compose <toolset-gcc:std>cxx1y : <cxxflags>-std=c++1y ; feature.compose <toolset-gcc:std>cxx14 : <cxxflags>-std=c++14 ; using clang : : : <cxxflags>-Wno-variadic-macros <cxxflags>-Wno-c99-extensions ; feature.subfeature toolset clang : std : cxx0x cxx11 cxx1y cxx14 : optional composite propagated ; feature.compose <toolset-clang:std>cxx0x : <cxxflags>-std=c++0x ; feature.compose <toolset-clang:std>cxx11 : <cxxflags>-std=c++11 ; feature.compose <toolset-clang:std>cxx1y : <cxxflags>-std=c++1y ; feature.compose <toolset-clang:std>cxx14 : <cxxflags>-std=c++14 ; This allows me to use toolset=clang (without -std) and toolset=clang-cxx11 (with -std=c++11). The 'requires' rule however caches the results of the configuration check when I run with toolset=clang, and then when I rerun with toolset=clang-cxx11, it uses the cached values, which is wrong. I use something like run test.cpp : : : [ requires cxx11_variadic_templates cxx11_template_aliases cxx11_hdr_type_traits cxx11_hdr_tuple ] ;

6 16

[hana] question
by Christophe Henry 22 Jun '15

22 Jun '15

Hi Louis, I'm experimenting with hana for the review and have one question. I can fold with boost::hana::fold.left(boost::mpl::vector<...>{}...) Do you have a way to iterate on elements of a mpl::set? Thanks, Christophe

2 1

[Boost] [Hana] Formal review for Hana
by Glen Fernandes 22 Jun '15

22 Jun '15

Dear Boost community, The formal review of Louis Dionne's Hana library begins today,10th June and ends on 24th June. Hana is a header-only library for C++ metaprogramming that provides facilities for computations on both types and values. It provides a superset of the functionality provided by Boost.MPL and Boost.Fusion but with more expressiveness, faster compilation times, and faster (or equal) run times. To dive right in to examples, please see the Quick start section of the library's documentation: http://ldionne.com/hana/index.html#tutorial-quickstart Hana makes use of C++14 language features and thus requires a C++14 conforming compiler. It is recommended you evaluate it with clang 3.5 or higher. Hana's source code is available on Github: https://github.com/ldionne/hana Full documentation is also viewable on Github: http://ldionne.github.io/hana To read the documentation offline: git clone http://github.com/ldionne/hana --branch=gh-pages doc/gh-pages For a gentle introduction to Hana, please see: 1. C++Now 2015: http://ldionne.github.io/hana-cppnow-2015 (slides) 2. C++Con 2014: https://youtu.be/L2SktfaJPuU (video) http://ldionne.github.io/hana-cppcon-2014 (slides) We encourage your participation in this review. At a minimum, kindly state: - Whether you believe the library should be accepted into Boost * Conditions for acceptance - Your name - Your knowledge of the problem domain. You are strongly encouraged to also provide additional information: - What is your evaluation of the library's: * Design * Implementation * Documentation * Tests * Usefulness - Did you attempt to use the library? If so: * Which compiler(s) * What was the experience? Any problems? - How much effort did you put into your evaluation of the review? We await your feedback! Best, Glen

7 33

Re: [boost] [Hana] Formal review
by David Sankel 22 Jun '15

22 Jun '15

On Wed, Jun 10, 2015 at 3:19 AM, Glen Fernandes <glen.fernandes(a)gmail.com> wrote: > - Whether you believe the library should be accepted into Boost > * Conditions for acceptance > Yes, I think it should be accepted into Boost. The one condition is that the library works with release versions of at least two different mainstream C++ compilers. More on that later... > - Your name > David J. Sankel > - Your knowledge of the problem domain. > I've written numerous libraries that make use of Boost.MPL and Boost.Fusion. I also have quite a bit of functional programming expertise. > > You are strongly encouraged to also provide additional information: > - What is your evaluation of the library's: > * Design > The core technique of combining value and type expressions is solid and makes metaprogramming easier and, as a bonus, improves compilation speeds. My one question, as I read though the implementation, is "can the core benefits of this library be achived with a simpler 'light' version of this implementation?". While I appreciate the attempt to encode a Haskell-style typeclass hierarchy, I feel like that is not the core competency of hana and should be a separate library and discussion. As it is, this is a 32k header mega library. I'd prefer several small, highly-targeted, highly-composable libraries. > * Implementation > The code itself looks to be well structured and well documented. Unfortunately hana only works with one compiler: clang. While I agree that Boost shouldn't need to support Visual C++ 6.0 anymore, I believe this is going too far in the opposite direction. The home page states that boost libraries "are intended to be widely useful, and usable across a broad spectrum of applications". I've always interpreted that statement to be in a practical rather than theoretical sense and I don't think hana meets that criteria. Many other Boost authors have made heroic efforts to meet that criteria and the reputation of Boost is due, in no small part, to those efforts. I do appreciate the argument that making use of new features encourages compiler implementers to implement then. I maintain, however, that this isn't Boost's job. Boost provides high quality libraries that the every-day Joe C++ developer can benefit from. That being my position on the issue, my acceptance vote is conditional on hana supporting at least two released versions of mainstream compilers. Given that gcc support seems pretty close, that shouldn't be hard to achieve. * Documentation > Looks good. > * Tests > I didn't evaluate these. I tried, but failed, to build the code and filed related issues. I'm assuming the problems are minor and straightforward to fix. * Usefulness > Maybe in a couple years for me. Without VS 2015 support at least, I'm going to be waiting a while. - Did you attempt to use the library? Yes. Started working through the getting started examples. > If so: > * Which compiler(s) > clang 3.6.1 > * What was the experience? Any problems? > Nothing more to add. I filed an issues for all problems encountered and they seemed minor. > - How much effort did you put into your evaluation of the review? > I attended both of Louis's talks, skimmed through the documentation, attempted to build, and read portions of the code. -- David Sankel

17 38

Attn: Volodya.. Re: [config] 'requres' doesn't take differing -std into account
by Rene Rivera 22 Jun '15

22 Jun '15

On Sun, Jun 21, 2015 at 8:11 PM, Edward Diener <eldiener(a)tropicsoft.com> wrote: > On 6/21/2015 10:19 AM, Peter Dimov wrote: > >> I have, in my user-config.jam, >> >> using gcc ; >> >> feature.subfeature toolset gcc : std : cxx0x cxx11 cxx1y cxx14 : >> optional composite propagated ; >> >> feature.compose <toolset-gcc:std>cxx0x : <cxxflags>-std=c++0x ; >> feature.compose <toolset-gcc:std>cxx11 : <cxxflags>-std=c++11 ; >> feature.compose <toolset-gcc:std>cxx1y : <cxxflags>-std=c++1y ; >> feature.compose <toolset-gcc:std>cxx14 : <cxxflags>-std=c++14 ; >> >> using clang : : : <cxxflags>-Wno-variadic-macros >> <cxxflags>-Wno-c99-extensions ; >> >> feature.subfeature toolset clang : std : cxx0x cxx11 cxx1y cxx14 : >> optional composite propagated ; >> >> feature.compose <toolset-clang:std>cxx0x : <cxxflags>-std=c++0x ; >> feature.compose <toolset-clang:std>cxx11 : <cxxflags>-std=c++11 ; >> feature.compose <toolset-clang:std>cxx1y : <cxxflags>-std=c++1y ; >> feature.compose <toolset-clang:std>cxx14 : <cxxflags>-std=c++14 ; >> >> This allows me to use toolset=clang (without -std) and >> toolset=clang-cxx11 (with -std=c++11). >> >> The 'requires' rule however caches the results of the configuration >> check when I run with toolset=clang, and then when I rerun with >> toolset=clang-cxx11, it uses the cached values, which is wrong. >> > > I believe the same problem is causing predef-check problems in the predef > library because I have seen local errors using predef-check which also says > that a previous calculation on another toolset has been cached and is being > reused, even when the toolset changes. Somehow the incorrect cached value > is being retained by Boost Build even when the toolset value changes and a > new calculation needs to be made. But like many other people I don't know > nearly enough about Boost Build to figure out what it is doing. I must confess I don't know the rationale for limiting the feature set for config checks. We have to see what Volodya says about this. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

1 0