Skip to content

improve Assignment operation #22

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

Merged
merged 3 commits into from
May 30, 2025
Merged

Conversation

cloutierMat
Copy link

@cloutierMat cloutierMat commented May 30, 2025

Motivation

As a follow up to #21. I wasn't super satisfied with the solution I found as it seemed to dangerously rely on a quasi-impossible to read regex and a big match/case.

The changes in this pr are utilizing the tools of airspeed a lot better and remove the responsibility of knowing each possible terms from Assignment and allow us to debug and add new terms if required in the future with more ease.

@cloutierMat cloutierMat requested review from simonrw and bentsku May 30, 2025 05:28
@cloutierMat cloutierMat marked this pull request as ready for review May 30, 2025 05:28
@@ -4,8 +4,8 @@


setup(
name="airspeed-ext",
version="0.6.8",
name="airspeed_ext",
Copy link
Author

Choose a reason for hiding this comment

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

I received a notice from PyPi after release the last package that we need to conform to PEP 625. My understanding is that this will solve the issue and won't have any side effects as far as installing and using the package.

Copy link

@bentsku bentsku left a comment

Choose a reason for hiding this comment

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

LGTM, this is neat 👍 it makes much better use of the internal, nice find! This is also help support the case in the comment with set($one.two().three = something), with a "function call term"!

And now the Assignment still looks pretty similar to before, thanks to that, and remove the old .split("."). Awesome 🚀

@cloutierMat cloutierMat merged commit 1a813b1 into master May 30, 2025
1 check 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