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 GetFreeVariables() overload to Expression #22145

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

RussTedrake
Copy link
Contributor

@RussTedrake RussTedrake commented Nov 8, 2024

We have Expression::GetVariables() and Formula::GetFreeVariables(). In #22091, we could see that this difference (which is mostly unnecessary) made the downstream code unnecessarily clunky. This simple overload resolves it.

+@cohnt for feature review, please.


This change is Reviewable

We have Expression::GetVariables() and Formula::GetFreeVariables().
In RobotLocomotion#22091, we could see that this difference (which is mostly
unnecessary) made the downstream code unnecessarily clunky. This
simple overload resolves it.
@RussTedrake RussTedrake added release notes: feature This pull request contains a new feature release notes: none This pull request should not be mentioned in the release notes and removed release notes: feature This pull request contains a new feature labels Nov 8, 2024
Copy link
Contributor

@cohnt cohnt left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: needs platform reviewer assigned, needs at least two assigned reviewers

@RussTedrake
Copy link
Contributor Author

+@sammy-tri for platform review, please.

Copy link
Contributor

@sammy-tri sammy-tri left a comment

Choose a reason for hiding this comment

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

:lgtm:

From looking at #22091 it's clear that this change improves readability there. I did a little digging to figure out if there was a deliberate reason for the different names and I couldn't immediately come up with anything. This has a slightly fishy smell to be but I can't figure out any reason to not merge it.

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: :shipit: complete! all discussions resolved, LGTM from assignees sammy-tri(platform),cohnt

@sammy-tri sammy-tri merged commit f859518 into RobotLocomotion:master Nov 11, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium release notes: none This pull request should not be mentioned in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants