Communication CFT Weekly [2025-03-24]

[LittleHuba]

Participants

• @LittleHuba
• Alexandru Iulian
• @armin-acn
• Braun Holger
• Haraga Mihai
• Hosch Markus
• @qor-lb
• @arsibo
• @vinodreddy-g

Agenda

1. API Mockup Sync
2. JSON library (Feature request for qualified json-parser #757)
3. Follow-Up
   • Core datatypes @qor-lb

Meeting Minutes

to 1.:

C++

No efforst currently done. Paused for json library.

Rust

First workshop this week
After workshop a PR is created with a greenfield approach for a new API
Testcases are created to show how this API can be used
Plugging this on top of mw::com and Iceoryx2 (not part of v0.5) will follow after
https://github.com/orgs/eclipse-score/discussions/720

Request from infrastructure community for support to improve toolchains and CI
-> Rust workgroup will support infra community starting from next month

to 2.:

• Option to only look into reading of json for now and ignore writing path
• For reading one impl with two bindings is feasible, for writing it is not (given persistency will need to write we do not want to go this direction)
• Feature request for both C++ and Rust
  • Proposal for chosen implementations:
    • tinyjson for Rust
    • nlohmann/json for C++
• Accompanying list to the FR to note findings on viability of the solutions

Feature request is shown to Technical lead circle and a call for contribution is done there

to 3.:

#678

• No implementation for full language barrier bridging of datatypes
• Concept: Define datatypes in one of the target languages and automatically generate bindings for second language
• Alternative approach: IDL to define datatype with memory layout and generation for both languages
  => Raise to architecture workshop to discuss how this shall be solved
  @ Hosch Markus to create FR in Rust workgroup
  @qor-lb to discuss in workshop