Added BoundedPlainSequences messages#14
Conversation
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
msg/BoundedSequencesNoStrings.msg
Outdated
| @@ -0,0 +1,32 @@ | |||
| # Bounded sequences of different types | |||
There was a problem hiding this comment.
@MiguelCompany if the core idea behind adding messages is to have bounded sequence of plain data types, consider making that explicit in the name e.g. BoundedPlainSequences, BoundedPODSequences or any meaningful name you like.
msg/UnboundedSequencesNoStrings.msg
Outdated
| @@ -0,0 +1,32 @@ | |||
| # Unbounded sequences of different types | |||
There was a problem hiding this comment.
@MiguelCompany if you have no use case for this message type, please don't add it.
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
Signed-off-by: Miguel Company <MiguelCompany@eprosima.com>
|
Alright, finally green. Going in! |
|
This is Steve your friendly build farmer here checking in. I don't know if it was this or ros2/rcl_interfaces#123, but the last nightly build shows quite a few failures in the test_communication package related to I'm not sure if this PR's CI builds included the |
|
@scpeters @hidmic It seems I see two different issues here:
|
Adding two message definitions with sequences of POD types