High number of integer_sequence/index_sequence implementations
Bunch of Boost libraries have their own integer_sequence/index_sequence implementation. Wouldn’t it be better if there was boost::integer_sequence/boost::index_sequence? boost\beast\core\detail\integer_sequence.hpp boost\callable_traits\detail\polyfills\make_index_sequence.hpp boost\context\detail\index_sequence.hpp boost\fusion\support\detail\index_sequence.hpp boost\mp11\integer_sequence.hpp boost\phoenix\core\detail\index_sequence.hpp (alias of fusion one) boost\poly_collection\detail\functional.hpp (uses mp11 one) boost\test\data\index_sequence.hpp boost\variant\detail\multivisitors_cpp11_based.hpp
Stephan T. Lavavej wrote:
[Nikita Kniazev]
Bunch of Boost libraries have their own integer_sequence/index_sequence implementation. Wouldn’t it be better if there was boost::integer_sequence/boost::index_sequence?
And how many of them are powered by __make_integer_seq (when available) for throughput?
I haven't bothered because for N=8192 the difference is between 1.0s and 0.7s and doing anything nontrivial with 8192 is probably going to fail anyway, but I might do so if only to be able to answer in the affirmative.
participants (4)
-
Nikita Kniazev
-
Peter Dimov
-
Stephan T. Lavavej
-
Vinnie Falco