-
-
Notifications
You must be signed in to change notification settings - Fork 36
did I GAT
this right?
#91
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #91 +/- ##
==========================================
+ Coverage 84.10% 84.16% +0.05%
==========================================
Files 3 3
Lines 1139 1143 +4
Branches 1139 1143 +4
==========================================
+ Hits 958 962 +4
Misses 120 120
Partials 61 61 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this looks good to me!
I will probably wait to merge this until PyO3 upstream bumps MSRV to 1.65 or higher, after which point we'll be good to make use of this here.
@davidhewitt Thanks for taking a look. Maybe a dumb question, but what is the advantage of gats over not gats? |
In some cases they enable patterns that aren't previously possible. Here, they're just a nice simplification because it removes the lifetime from the trait ident and usage sites to be internal to the implementations. |
@davidhewitt thanks so much! rust is a wild language; I have this sense that rust is very mind-bending to people coming from cpp/java/python/. |
@davidhewitt does this pr (PyO3/pyo3#5171) mean we are good to go here? |
@davidhewitt is this what you intended to change based on the TODOs?