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

DM-32663 Assume Field is operating on Config instance #62

Merged
merged 1 commit into from Nov 19, 2021

Conversation

natelust
Copy link
Contributor

In almost all cases a Field is operating on a config instance,
and there should be no need to check on every invocation of
get. Fallback to a check if normal operation does not
succeed.

In almost all cases a Field is operating on a config instance,
and there should be no need to check on every invocation of
__get__. Fallback to a check if normal operation does not
succeed.
Copy link
Member

@TallJimbo TallJimbo left a comment

Choose a reason for hiding this comment

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

I'm kind of curious whether this is the right behavior when instance is not None and not a Config, but it's the old behavior and it's probably best not to try to change that in the interest of getting this done quickly.

@natelust
Copy link
Contributor Author

Yeah I don't know that I agree with it either, but I didn't want to rock the boat and just make the performance change now

@natelust natelust merged commit d1925c9 into master Nov 19, 2021
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.

None yet

2 participants