tzlaine/flat_map issues and pull requests

#37 - Performance issue in find function.

Issue - State: open - Opened by Febbe 8 months ago

#37 - Performance issue in find function.

Issue - State: open - Opened by Febbe 8 months ago

#36 - Should __ref_pair::__pair_type just remove_reference rather than remove_cvref?

Issue - State: open - Opened by swolchok over 2 years ago

#36 - Should __ref_pair::__pair_type just remove_reference rather than remove_cvref?

Issue - State: open - Opened by swolchok over 2 years ago

#35 - Raise with LWG: Make `containers` explicitly destructurable

Issue - State: closed - Opened by tzlaine over 2 years ago - 1 comment

#35 - Raise with LWG: Make `containers` explicitly destructurable

Issue - State: closed - Opened by tzlaine over 2 years ago - 1 comment

#34 - Raise with LWG: Where to put `sorted_unique_t` and `sorted_equivalent_t`?

Issue - State: closed - Opened by tzlaine over 2 years ago - 1 comment

#34 - Raise with LWG: Where to put `sorted_unique_t` and `sorted_equivalent_t`?

Issue - State: closed - Opened by tzlaine over 2 years ago - 1 comment

#33 - Raise with LWG: Change the constraint on non-`from_range_t` range ctors?

Issue - State: closed - Opened by tzlaine over 2 years ago - 1 comment

#33 - Raise with LWG: Change the constraint on non-`from_range_t` range ctors?

Issue - State: closed - Opened by tzlaine over 2 years ago - 1 comment

#32 - Raise with LWG: Does hardcoded `size_t` pose problems for containers with extended integral sizes?

Issue - State: closed - Opened by tzlaine almost 3 years ago

#32 - Raise with LWG: Does hardcoded `size_t` pose problems for containers with extended integral sizes?

Issue - State: closed - Opened by tzlaine almost 3 years ago

#31 - Raise with LWG: Do we need to explicitly say that you cannot cast away constness from `keys()` and `values()`?

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#31 - Raise with LWG: Do we need to explicitly say that you cannot cast away constness from `keys()` and `values()`?

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#30 - Raise with LWG: Italicize exposition-only members?

Issue - State: closed - Opened by tzlaine almost 3 years ago

#30 - Raise with LWG: Italicize exposition-only members?

Issue - State: closed - Opened by tzlaine almost 3 years ago

#29 - Rewrite in [container.adaptors.general] needs more fine-grained changed{} markup

Issue - State: closed - Opened by tzlaine almost 3 years ago

#29 - Rewrite in [container.adaptors.general] needs more fine-grained changed{} markup

Issue - State: closed - Opened by tzlaine almost 3 years ago

#28 - Flat set updates for erase_if and ranges_to

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#28 - Flat set updates for erase_if and ranges_to

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#27 - flat_map R8 the final chapter

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#27 - flat_map R8 the final chapter

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#26 - Raise with LWG: Barry R. suggested removing the special formatter wording for flat{mulit,}map, and adding those types with the formatter for map, etc.

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#26 - Raise with LWG: Barry R. suggested removing the special formatter wording for flat{mulit,}map, and adding those types with the formatter for map, etc.

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#25 - Raise with LWG: [container.adaptors.general]/2 was re-written, and is sketchy at best.

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#25 - Raise with LWG: [container.adaptors.general]/2 was re-written, and is sketchy at best.

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#24 - Raise with LWG: collapse new heterogeneous ops into their other overloads in definitions?

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#24 - Raise with LWG: collapse new heterogeneous ops into their other overloads in definitions?

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#23 - Flat set - pile of additional updates

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#23 - Flat set - pile of additional updates

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#22 - flatmultimap overview stable name typo should flatmultimap.overview

Issue - State: closed - Opened by JeffGarland almost 3 years ago - 1 comment

#22 - flatmultimap overview stable name typo should flatmultimap.overview

Issue - State: closed - Opened by JeffGarland almost 3 years ago - 1 comment

#21 - Raise with LWG: the `ranges::input_range R` ctors might need separate wording

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#21 - Raise with LWG: the `ranges::input_range R` ctors might need separate wording

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#20 - Flat set updates

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#20 - Flat set updates

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#19 - ranges::to()

Issue - State: closed - Opened by tzlaine almost 3 years ago

#19 - ranges::to()

Issue - State: closed - Opened by tzlaine almost 3 years ago

#18 - std::begin(c) -> c.begin() for consistency

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#18 - std::begin(c) -> c.begin() for consistency

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#17 - Rebase on N4910, in detail.

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#17 - Rebase on N4910, in detail.

Issue - State: closed - Opened by tzlaine almost 3 years ago - 1 comment

#16 - update to stable name references (proposed design incomplete after re…

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#16 - update to stable name references (proposed design incomplete after re…

Pull Request - State: closed - Opened by JeffGarland almost 3 years ago

#15 - Heterogenous ops on a branch

Issue - State: closed - Opened by tzlaine almost 3 years ago

#15 - Heterogenous ops on a branch

Issue - State: closed - Opened by tzlaine almost 3 years ago

#14 - What's the license of the reference implementation code?

Issue - State: closed - Opened by Kazade almost 3 years ago - 1 comment

#14 - What's the license of the reference implementation code?

Issue - State: closed - Opened by Kazade almost 3 years ago - 1 comment

#13 - first cut at wording and revisions updates from Dec 2020 LWG meeting

Pull Request - State: closed - Opened by JeffGarland almost 4 years ago - 2 comments

#13 - first cut at wording and revisions updates from Dec 2020 LWG meeting

Pull Request - State: closed - Opened by JeffGarland almost 4 years ago - 2 comments

#12 - Make data members protected

Issue - State: closed - Opened by dimztimz almost 5 years ago

#12 - Make data members protected

Issue - State: closed - Opened by dimztimz almost 5 years ago

#11 - `flat_set.insert(first, last)` cannot possibly happen in linear time

Issue - State: closed - Opened by Quuxplusone almost 6 years ago - 2 comments

#11 - `flat_set.insert(first, last)` cannot possibly happen in linear time

Issue - State: closed - Opened by Quuxplusone almost 6 years ago - 2 comments

#10 - `ranges::unique(begin(), end(), value_comp())` is wrong

Issue - State: closed - Opened by Quuxplusone almost 6 years ago

#10 - `ranges::unique(begin(), end(), value_comp())` is wrong

Issue - State: closed - Opened by Quuxplusone almost 6 years ago

#9 - Deduction guides taking `Container` need to be completely re-thought

Issue - State: closed - Opened by Quuxplusone about 6 years ago

#9 - Deduction guides taking `Container` need to be completely re-thought

Issue - State: closed - Opened by Quuxplusone about 6 years ago

#8 - Allow custom search algortihm function (not just custom compare function)

Issue - State: closed - Opened by dimztimz almost 7 years ago - 1 comment

#8 - Allow custom search algortihm function (not just custom compare function)

Issue - State: closed - Opened by dimztimz almost 7 years ago - 1 comment

#7 - specify comparison operators, but don't place them in the synopsis

Issue - State: closed - Opened by tzlaine over 7 years ago

#7 - specify comparison operators, but don't place them in the synopsis

Issue - State: closed - Opened by tzlaine over 7 years ago

#6 - in the perf tests, sample from an array of maps to decrease cache coherency

Issue - State: closed - Opened by tzlaine over 7 years ago

#5 - type alias

Issue - State: closed - Opened by tzlaine over 7 years ago

#4 - use proxy iterator and pair-of-refs value_type for flat_map

Issue - State: closed - Opened by tzlaine over 7 years ago - 1 comment

#3 - add split_flat_map, use Ranges TS style zip iterator

Issue - State: closed - Opened by tzlaine over 7 years ago - 1 comment

#2 - rvalue ref quals on functions that move out the contents

Issue - State: closed - Opened by tzlaine over 7 years ago

#1 - deduction guides

Issue - State: closed - Opened by tzlaine over 7 years ago - 1 comment

GitHub / tzlaine/flat_map issues and pull requests