Skip to content

Conversation

@acmorrow
Copy link
Member

@lia-viam - Speculatively putting this PR up while I wait for a workflow run to validate that it gets the results I need. If so, I'd like to merge this and tag an 0.8.1 release. I'll follow up either way on this PR with results.

@acmorrow acmorrow requested a review from lia-viam April 11, 2025 19:23
@acmorrow acmorrow requested a review from a team as a code owner April 11, 2025 19:23
@acmorrow acmorrow requested review from njooma and removed request for a team April 11, 2025 19:23
@lia-viam
Copy link
Collaborator

the bullseye failure is expected, bookworm is worth re-running but not a blocker

Copy link
Member Author

@acmorrow acmorrow left a comment

Choose a reason for hiding this comment

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

@lia-viam - Updated, PTAL. This fixes the compilation issue with VS2019.


/// @brief An ordered list of plan steps.
struct steps steps;
steps steps;
Copy link
Collaborator

Choose a reason for hiding this comment

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

looks like this is still causing issues, now with additional compilers. a couple thoughts. so i think usually our alias declarations would use camel case, and if the declarations above were using Step = ... and using Steps = ... there would be no issue here.

that said, i'm sort of thinking we should just write std::vector<[Ss]tep> and call it a day. the alias for unordered_map feels ergonomically justified, a vector alias less so. and generally speaking we don't have many instances in the sdk of doing using meows = std::vector<meow> and i suppose i'm not crazy about the practice in general.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, that makes sense. I've made that change.

@acmorrow
Copy link
Member Author

Updated, PTAL. Hopefully the builders are happier with this, i'm trying it on VS 2019 right now as well.

Copy link
Collaborator

@lia-viam lia-viam left a comment

Choose a reason for hiding this comment

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

lgtm, good to merge if the builds pass.

@acmorrow acmorrow merged commit 7ba50e0 into viamrobotics:main Apr 14, 2025
12 of 13 checks passed
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.

2 participants