-
Notifications
You must be signed in to change notification settings - Fork 113
[pointer] Make invariants opaque, more ergonomic #1895
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
Conversation
Merge commits are not allowed on this repository
@jswrenn I didn't update any methods which modify two of three invariants. Any galaxy brain ideas on how to make those ergonomic? The best I could come up with was yet another set of associated types e.g.: type RetainAliasing<A: Alignment, V: Validity> = ...; ...but that's not forwards-compatible with adding new invariant types. |
7c245c5
to
062b71a
Compare
3ab2c00
to
cf218f6
Compare
9eab1bd
to
39d2339
Compare
cf218f6
to
77362c9
Compare
39d2339
to
da4069e
Compare
77362c9
to
25de780
Compare
da4069e
to
2172f24
Compare
25de780
to
d96d763
Compare
2172f24
to
2a92f9f
Compare
d96d763
to
471f4a9
Compare
2a92f9f
to
9e69c15
Compare
471f4a9
to
25ddf05
Compare
9e69c15
to
19875da
Compare
25ddf05
to
87a434a
Compare
19875da
to
029d5d6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1895 +/- ##
==========================================
- Coverage 87.65% 87.64% -0.02%
==========================================
Files 17 17
Lines 5964 5956 -8
==========================================
- Hits 5228 5220 -8
Misses 736 736 ☔ View full report in Codecov by Sentry. |
Closes #1876