Skip to content

Allow for implicitly convertable loggers as well (backport #2922)#2934

Closed
mergify[bot] wants to merge 1 commit intojazzyfrom
mergify/bp/jazzy/pr-2922
Closed

Allow for implicitly convertable loggers as well (backport #2922)#2934
mergify[bot] wants to merge 1 commit intojazzyfrom
mergify/bp/jazzy/pr-2922

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Aug 13, 2025

Description

This way I can inherit from rclpp::Logger and still pass it to the logger macros.

Is this user-facing behavior change?

Backwards compatible

Did you use Generative AI?

No

Additional Information

If accepted I would like to have this backported to active distros as well.


This is an automatic backport of pull request #2922 done by Mergify.

* Allow for implicitly convertable loggers as well

Signed-off-by: Tim Clephas <tim.clephas@nobleo.nl>

* Test implicitly convertable logger

Signed-off-by: Tim Clephas <tim.clephas@nobleo.nl>

* This can be simplified now

Signed-off-by: Tim Clephas <tim.clephas@nobleo.nl>

* fixup! This can be simplified now

Signed-off-by: Tim Clephas <tim.clephas@nobleo.nl>

---------

Signed-off-by: Tim Clephas <tim.clephas@nobleo.nl>
(cherry picked from commit e615c7c)

# Conflicts:
#	rclcpp/include/rclcpp/logging.hpp
@mergify mergify bot added the conflicts label Aug 13, 2025
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Aug 13, 2025

Cherry-pick of e615c7c has failed:

On branch mergify/bp/jazzy/pr-2922
Your branch is up to date with 'origin/jazzy'.

You are currently cherry-picking commit e615c7c.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   rclcpp/test/rclcpp/test_logging.cpp

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   rclcpp/include/rclcpp/logging.hpp

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@jmachowinski
Copy link
Copy Markdown
Collaborator

closing, as automatic backport is not possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants