libcruft-util/alloc/raw
Danny Robson b23c274742 alloc/foreign: don't use a null base pointer
We can't use null for the proxy view passed to the successor allocators
because it triggers undefined behaviour.
2018-03-05 15:58:36 +11:00
..
aligned alloc/foreign: don't use a null base pointer 2018-03-05 15:58:36 +11:00
affix.cpp Merge branch 'master' into coord 2017-11-23 17:24:11 +11:00
affix.hpp alloc: prefer std::byte representations for iterators 2018-02-28 17:55:56 +11:00
dynamic.hpp alloc: add aligned::foreign allocator 2018-03-02 12:21:38 +11:00
fallback.cpp alloc: seperate out the raw allocators from the adapters 2017-08-29 16:53:11 +10:00
fallback.hpp alloc: seperate out the raw allocators from the adapters 2017-08-29 16:53:11 +10:00
linear.cpp alloc: add aligned::foreign allocator 2018-03-02 12:21:38 +11:00
linear.hpp alloc: add aligned::foreign allocator 2018-03-02 12:21:38 +11:00
malloc.cpp Merge branch 'master' into coord 2017-11-23 17:24:11 +11:00
malloc.hpp alloc: seperate out the raw allocators from the adapters 2017-08-29 16:53:11 +10:00
null.cpp alloc: prefer std::byte representations for iterators 2018-02-28 17:55:56 +11:00
null.hpp alloc: prefer std::byte representations for iterators 2018-02-28 17:55:56 +11:00
stack.cpp alloc: add aligned::foreign allocator 2018-03-02 12:21:38 +11:00
stack.hpp alloc: add aligned::foreign allocator 2018-03-02 12:21:38 +11:00
traits.hpp alloc: add aligned::foreign allocator 2018-03-02 12:21:38 +11:00