Doc n warnings may 25 #146
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remove warnings thread the opaque_access argument to avoid Library.indirect_accessor
ybertot
force-pushed
the
doc-n-warnings-May-25
branch
from
66da48c to
96b1ddd
Compare
Collaborator
Author
|
@SkySkimmer, can you please check that I used the "opaque_access" feature as you intended when you added the deprecation warning on |
SkySkimmer
approved these changes
Jun 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
no more warning when executing rocq code for the tests
no more warning when compiling ml code (use of a threaded opaque_access instead of a Library.indirect_accessor)
Refreshed the documentation, including a suggestion from T. Bourke, and more compatible with the rocq renaming.