You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As explained in ros2#1254, there's conceptually no way to implement RCL
allocators in terms of C++ allocators. Since allocator_common can't
be fixed, delete it and inline calls to rcl_get_default_allocator at
the call sites. Since this would introduce surprising behavior for
custom allocator users (using system malloc when a custom allocator
is requested), add compile-time assertions checking for non-default
allocators. Since there's other blocking bugs for allocator use
(ros2#1061), this shouldn't break existing users.
Technically, we could roll back a lot of templating on allocator and
explicitly use std::allocator<void> in all classes. I have refrained
from doing so because you might have plans with this code, but if you
concur, I'll be more than happy to de-template all these classes to
simplify the code.
0 commit comments