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
Currently, rosidl_runtime_c implements copy functions for various basic types, but does not consider move semantics-related APIs. Theoretically, providing move-related APIs could significantly improve the convenience and performance of applications built upon it.
For example, I am currently implementing some interoperability with other frameworks based on rosidl_typesupport_introspection_c's typesupport, but the lack of move semantics forces me to implement the relevant move functionality within my framework, which is not elegant.
Implementation Considerations
I have carefully reviewed the implementation in rosidl_runtime_c. The move method should not differ significantly from the copy method; only minor adjustments are needed to address the semantics.
If the discussion concludes that this feature is necessary, I will begin implementation in the coming weeks.
The text was updated successfully, but these errors were encountered:
Feature request
Feature Description
Currently, rosidl_runtime_c implements copy functions for various basic types, but does not consider move semantics-related APIs. Theoretically, providing move-related APIs could significantly improve the convenience and performance of applications built upon it.
For example, I am currently implementing some interoperability with other frameworks based on rosidl_typesupport_introspection_c's typesupport, but the lack of move semantics forces me to implement the relevant move functionality within my framework, which is not elegant.
Implementation Considerations
I have carefully reviewed the implementation in rosidl_runtime_c. The move method should not differ significantly from the copy method; only minor adjustments are needed to address the semantics.
If the discussion concludes that this feature is necessary, I will begin implementation in the coming weeks.
The text was updated successfully, but these errors were encountered: