Skip to content

add new features for Kilted Kaiju. #5346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: rolling
Choose a base branch
from

Conversation

fujitatomoya
Copy link
Collaborator

follow up #5319 (review)

Copy link
Collaborator Author

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding a couple of new features to Kilted Kaiju release.

@christophebedard @ahcorde can you review?

Copy link

HTML artifacts: https://github.com/ros2/ros2_documentation/actions/runs/14652626750/artifacts/3005787255.

To view the resulting site:

  1. Click on the above link to download the artifacts archive
  2. Extract it
  3. Open html-artifacts-5346/index.html in your favorite browser

Static Type Checking
""""""""""""""""""""

Static type checking improvements to ensure that user application is using variables and functions correctly.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there something we can link to for more info, especially from the point of view of a user of rclpy?

Maybe @InvincibleRMC has a suggestion?

Copy link

@InvincibleRMC InvincibleRMC Apr 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main things I think users would care about would be the introduction of type hints into the Actions API. Implementation of generics in pub/sub/client/server/actions, Future/Task, and Parameter. Finally I think the introduction of type stubs for the underlying C++ implementation in _rclpy_pybind11.pyi. The last one is probably is more useful for maintainers/developers of rclpy so I am not sure if it would be necessary to include.

EventsExecutor
""""""""""""""

Support an experimental event executor to rclpy.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Support an experimental event executor to rclpy.
Support an experimental events executor for ``rclpy``, which is a port of the original ``rclcpp`` events executor concept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants