-
Notifications
You must be signed in to change notification settings - Fork 391
2021 09 02 Eclipse iceoryx developer meetup
elfenpiff edited this page Sep 2, 2021
·
2 revisions
Date: 2021/09/02
Time: 17:00 CET
Link: https://eclipse.zoom.us/j/95918504483?pwd=RWM5Y1pkeStKVDZsU09EY1hnclREUT09
- Christian Eltzschig, Apex.AI
- Dietrich Krönke, Apex.AI
- Simon Hoinkis, Apex.AI
- Roman Sokolkov, Apex.AI
- Marika Lehmann, Apex.AI
- Indra
- General: Are there other agenda points?, 2 mins
- Does anyone would like to contribute a feature?, 2 mins
- Types with dynamic size, Christian see design document pull request, 10 mins
- clang-tidy cleanup, next steps, Dietrich
- ABI strategy, Dietrich
- Stack allocator for
std::vector, Indra
- & 6.
- Christian extends design document to explain the pitfalls of custom STL allocators.
- STL container are using internally pointers which are not inter process capable.
- sending STL containers requires some kind of serialization within iceoryx
- Simon introduced custom clang-tidy rule for noexcept
- noexcept is not reliable detected for destructors
- noexcept(true) for destructors from C++17: https://en.cppreference.com/w/cpp/language/noexcept_spec
- clang-format CI target introduced by Roman
- clang-tidy should ignore google test warnings (
TEST_Ffixture missing copy/move ctor) - current clang-tidy CI linter ignores unit/integrationtests
- clang-tidy c-binding cannot detect language C/C++ since the headers are used in C++ for the implementation and in C from the user code - one header two languages
- API/ABI stability is required from ROS2
- we can break the API/ABI with a patch release when it is coordinates with open robotics
- ROS2 rolling release allows API/ABI breakage but dependencies to iceoryx have to be taken care of
- ABI compatibility test for the CI would be perfect
- message: be careful with the release branches
- maybe introduce rolling release branch for ROS2 rolling release