Skip to main content

Timeline for Constexpr flat_multimap

Current License: CC BY-SA 4.0

12 events
when toggle format what by license comment
Jul 9, 2023 at 16:27 comment added FreezePhoenix As far as I can tell, none of the major compilers have implemented flat_map (or flat_multimap), presumably because of the iterator issue. One of them had implemented flat_set, because that's simple and is only a single vector.
Jun 21, 2023 at 22:40 comment added Cris Luengo @Davislor I have done that many times, and hated it every time. I'm so happy with modern C++, I'm never going back to C.
Jun 21, 2023 at 20:54 comment added Davislor @CrisLuengo Wait until you typedef a function pointer.
Jun 21, 2023 at 13:02 vote accept FreezePhoenix
Jun 21, 2023 at 13:01 vote accept FreezePhoenix
Jun 21, 2023 at 13:01
Jun 21, 2023 at 3:01 comment added Cris Luengo Typedef vs using is a minor issue, but it was the first thing that tripped me. Using is so much easier to read IMO.
Jun 21, 2023 at 0:33 comment added FreezePhoenix There doesn't seem to be a STL way to implement the zipped iterator required for the iterators with 2 separate containers.
Jun 20, 2023 at 22:30 comment added FreezePhoenix Oops! I missed a few C() when I switched over to comparator. My bad!
Jun 20, 2023 at 21:32 history edited G. Sliepen CC BY-SA 4.0
added 205 characters in body
Jun 20, 2023 at 21:14 comment added Davislor I believe the move constructor and move assignment are correctly noexcept. They can be implemented with std::swap, which is constexpr and noexcept in C++20. The default constructor also only needs the default constructor of std::vector, which is constexpr and noexcept.
Jun 20, 2023 at 19:26 history edited G. Sliepen CC BY-SA 4.0
added 5 characters in body
Jun 20, 2023 at 19:21 history answered G. Sliepen CC BY-SA 4.0