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, in rosidl message type traits, there is no way to access the name of the message as a constexpr. The :name() function provides a const char* access to the name, which is not the same as constexpr.
This feature is needed when writing pythind typecasters. The macro PYBIND11_TYPE_CASTER(cpp::msg::type, const_name(msg_name)) requires access to a constexpr msg_name which is not the same as const char*. That name is an optional argument and is used as a docstring internally, but it would be nice to have it populated.
Implementation considerations
We could add a new global member like : constexpr const char[] complete_name = "geometry_msgs/msg/Quaternion";
The text was updated successfully, but these errors were encountered:
Feature request
Feature description
Currently, in rosidl message type traits, there is no way to access the name of the message as a
constexpr
. The:name()
function provides aconst char*
access to the name, which is not the same asconstexpr
.This feature is needed when writing pythind typecasters. The macro
PYBIND11_TYPE_CASTER(cpp::msg::type, const_name(msg_name))
requires access to aconstexpr msg_name
which is not the same asconst char*
. That name is an optional argument and is used as a docstring internally, but it would be nice to have it populated.Implementation considerations
We could add a new global member like :
constexpr const char[] complete_name = "geometry_msgs/msg/Quaternion"
;The text was updated successfully, but these errors were encountered: