Ion Gaztañaga comments

Results 61 comments of


                                            Ion Gaztañaga

KeyNodeCompare default constructor requirement

Thanks for the report. This is the same issue that was recently fixed: https://github.com/boostorg/container/issues/275

unrecognized command-line option ‘-fno-limit-debug-info’

This does not seem a Boost.Container issue as the compiler commands and flags are not produced by this library.

unrecognized command-line option ‘-fno-limit-debug-info’

Closing the bug as "not a defect"

flat_multimap::emplace not sorting elements under GCC

Please check the following commit, it should fix the issue: https://github.com/boostorg/container/commit/20ad12f20e661978e90dc7f36d8ab8ac05e5a5a9

flat_multimap::emplace not sorting elements under GCC

Closing this as fixed after the commit. Thanks for the report.

Support 'pure' (single pass) input_iterators

Boost.Container, at least sequence containers, should support "assign" from input iterators and that is tested in the library tests. Do you have an example that can reproduce the problem?

Support 'pure' (single pass) input_iterators

Closing this issue as assign from input iterator is already checked.

Support 'pure' (single pass) input_iterators

It's implemented using overloads and SFINAE. The function for input iterators is this: https://github.com/boostorg/container/blob/develop/include/boost/container/vector.hpp#L1320

Support 'pure' (single pass) input_iterators

Closing this issue as input iterators are implemented and and tested (https://github.com/boostorg/container/blob/develop/test/vector_test.hpp#L491)

boost::container::flat_map force_copy violates strict-aliasing rule

Thanks for the report. The strict aliasing violation was needed only for ancient compilers so the following commit removes it for C++11 o newer: https://github.com/boostorg/container/commit/20ad12f20e661978e90dc7f36d8ab8ac05e5a5a9