Skip to content
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

Add check_argument_types #130

Merged
merged 1 commit into from
Oct 15, 2015
Merged

Add check_argument_types #130

merged 1 commit into from
Oct 15, 2015

Conversation

esteve
Copy link
Member

@esteve esteve commented Oct 14, 2015

This PR adds a new template (check_argument_types) that checks both the arity and the types of the arguments of a given functor. There's no need to check the arity explicitly any more.

@esteve esteve added the in progress Actively being worked on (Kanban column) label Oct 14, 2015
@esteve
Copy link
Member Author

esteve commented Oct 14, 2015

@esteve esteve added in review Waiting for review (Kanban column) and removed in progress Actively being worked on (Kanban column) labels Oct 14, 2015
@esteve esteve self-assigned this Oct 14, 2015
@esteve
Copy link
Member Author

esteve commented Oct 14, 2015

The Windows CI job built fine and the test_function_traits tests pass:

http://ci.ros2.org/job/ros2_batch_ci_windows/489/testReport/%28root%29/TestFunctionTraits/

I just squashed the commits, this should be ok to merge.

struct check_argument_types
{
static constexpr bool value = check_argument_types_recursive<arity_comparator<
sizeof ... (Last) +1, FunctorT>::value, FunctorT, First, Last ...>::value;
Copy link
Member

Choose a reason for hiding this comment

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

The indentation looks a bit weird. Could the previous line be wrapped after the first <? Doesn't the +1 in this line need a space between?

Copy link
Member Author

Choose a reason for hiding this comment

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

I ran it through uncrustify and it kept complaining about + 1 being invalid. I don't like the way it looks now, but makes uncrustify happy.

I'll update the wrapping for the above line.

@esteve esteve force-pushed the cleaner-sfinae branch 2 times, most recently from ec69e88 to 2766fa1 Compare October 15, 2015 00:38
@esteve
Copy link
Member Author

esteve commented Oct 15, 2015

I've updated the PR to make the code a bit more readable, CI job:

http://ci.ros2.org/job/ros2_batch_ci_windows/494/

@esteve
Copy link
Member Author

esteve commented Oct 15, 2015

@dirk-thomas @jacquelinekay @tfoote @wjwwood This PR should be ready for merging, builds fine on Windows and doesn't break the compiler.

@wjwwood
Copy link
Member

wjwwood commented Oct 15, 2015

lgtm

esteve added a commit that referenced this pull request Oct 15, 2015
@esteve esteve merged commit 535008f into master Oct 15, 2015
@esteve esteve removed the in review Waiting for review (Kanban column) label Oct 15, 2015
@esteve esteve deleted the cleaner-sfinae branch October 15, 2015 20:40

static_assert(
!rclcpp::check_argument_types<decltype(func_two_ints), bool, int>::value,
"Functor accepts two ints as arguments");
Copy link
Member

Choose a reason for hiding this comment

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

Text does not match checked assertion.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done e2ade1f

nnmm pushed a commit to ApexAI/rclcpp that referenced this pull request Jul 9, 2022
DensoADAS pushed a commit to DensoADAS/rclcpp that referenced this pull request Aug 5, 2022
* ros2GH-138 Move calculation of bag size

- previously in rosbag2::Info
- now in storage plugin

* ros2GH-130 Add rosbag2_bag_v2_plugins package

-This package will contain storage and converter plugins

* ros2GH-131 don't build plugins on Windows

* ros2GH-129 Add function to be generated

- massive if/else between all message types
- will be generated similar to ros1_bridge plugin

* ros2GH-138 Write storage plugin for rosbag v2 bags

* ros2GH-138 Make sure that no attempt to create a converter is made when trying to read a rsbag v2 bag file

* ros2GH-138 Add play end-to-end test for rosbag v2 plugin

* ros2GH-138 Use cmake files to find ros1 packages

- Use files from ros1_bridge via PkgConfig

* ros2GH-138 Add generator code

* ros2GH-141 Add initial version of vendor package

* ros2GH-141 Improve vendor package to build on Mac

* ros2GH-138 Cleanup CMakeLists

* ros2GH-141 Use unmanaged Instance of class-loader

- managed instance somehow isn't available for gcc 6.3

* ros2GH-141 Reduce patch and copy new toplevle CMakeLists by hand

* ros2GH-141 Fix Shared Instance usage

* ros2GH-141 Improve maintainability of vendor package

- Document what patches do and why changes are necessary
- Load ros1 packages through cmake macro
- Do not export ros1 packages via ament
- use commit hash of current master which is more stable than using melodic-devel

* ros2GH-138 Link against rclcpp - necessary for ros1_bridge

* ros2GH-138 Avoid crash when trying to play v2 bags which contain unknown message types

* ros2GH-138 Add CLI -s <storage_id> option to ros2 bag info and use it in rosbag2::info

- this allows ros2 bag info to work also when the yaml metadata file does not exsist
- this is always the case for rosbag1 bagfiles
- it could also happen for sqlite or other storage based bagfiles

* ros2GH-138 Add end-to-end info test for rosbag v2 files

* ros2GH-138 Add unit tests to rosbag_storage

* ros2GH-138 Add method to extract filename from path to FilesystemHelpers

* ros2GH-138 Add proper logging for topics which cannot be converted

* ros2GH-138 Improve finding dependencies of ros1

* ros2GH-141 Explicitly import transitive dependencies of vendor package

* ros2GH-138 Skip tests via ament if ros1 is not available

* ros2GH-133 First split of plugins

* ros2GH-133 Write serialized rosbag message

* ros2GH-133 Improve converter plugin

- move generation templates outside of plugin folders as both
  plugins need it
- use ros::serialization routines to deserialize the ros message

* ros2GH-133 Add plugin to be found by pluginlib

* ros2GH-133 Remove empty check in converter

- With the rosbag_v2_converter_plugin, we don't need to treat
  rosbag_v2 storage any different

* ros2GH-133 Assert serialization format in unit tests for storage

* ros2GH-133 Delete superfluous include folder

- Only needed if we want to link against the library

* ros2GH-133 get_all_topics_and_types returns only valid ros2 types

- This is necessary as the information is used by rosbag2_transport
- ros2 bag info still shows all topics and types
- rosbag::View::getConnections() can return multiple connections corresponding to the same topic

* ros2GH-133 Improve end to end test

- use a bagfile with messages not known to ros2

* ros2GH-133 Reformulate info message in case of missing ros1-ros2 mapping for a topic

* ros2GH-14 Find messages first

* Explicitly print message when on Windows

Co-Authored-By: Martin-Idel-SI <external.Martin.Idel@bosch-si.com>

* ros2GH-14 Refactor rosbag_storage vendor package

- Improve toplevel CMakeLists
- Put all patches into a resource subfolder

* ros2GH-14 Reflect renames of converter interfaces

* ros2GH-156 Workaround for path problems

* ros2GH-156 Add documentation for plugin

* ros2GH-156 Fix the pluginlib version to greater 2

* ros2GH-156 Prohibit CMake from declaring paths as system paths

This switches the order of ros2 and ros1 directories
resulting in build failures

* ros2GH-156 Prohibit system include paths for rosbag plugins

This can lead to switching ros1 and ros2 include paths resulting
in missing symbols as the wrong pluginlib gets included

* ros2GH-14 Split patches

* make README more verbose

* add plugin specific readme

* more readme for bag_v2 plugin
mauropasse pushed a commit to mauropasse/rclcpp that referenced this pull request Nov 29, 2023
…ability-to-intra-process-pub-sub-irobot/humble

Add transient local durability to intra process pub sub irobot/humble
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