-
Notifications
You must be signed in to change notification settings - Fork 108
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
Make Ptr
invariants opaque and more ergonomic
#1876
Comments
joshlf
added a commit
that referenced
this issue
Oct 12, 2024
joshlf
added a commit
that referenced
this issue
Oct 12, 2024
joshlf
added a commit
that referenced
this issue
Oct 13, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
joshlf
added a commit
that referenced
this issue
Oct 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once we publish 0.9, which will have a sufficiently high MSRV that we have access to GAT, we implement the following design. This will permit all concrete
Invariants
types to be private. This, in turn, means that we can preserve the ability to make future changes to how we represent invariants, or even add new invariants.The text was updated successfully, but these errors were encountered: