Fix examples of opaque types #7259
Merged
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.
The bug in
Logarithm
was reported by @wks on gitter.Perhaps in both cases, it is not obvious that the operator on the right hand side is the one from the underlying type.
Especially in the second case, where
ReadWrite
must be defined asReadOnly | WriteOnly
insideAccess
, but the equivalent defined outsideAccess
would beReadOnly & WriteOnly
.