Publicly export Capabilities and ExtensionsList struct
#2101
Conversation
This file contains 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
It was already exposed via the CapabilitiesSource::get_capabalities method anyway, it was just that the type was not publicy reachable
|
Oh yeah. Not that I needed it now. But I saw |
faern
force-pushed
the
re-export-capabilities
branch
from
94eda3a
to
21c9bf5
Compare
faern
changed the title
Capabilities structCapabilities and ExtensionsList struct
est31
approved these changes
Feb 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It was already exposed via the
CapabilitiesSource::get_capabalitiesmethod anyway, but the struct itself was not public. So a library user could not refer to the type, neither could they click their way through to the struct documentation.See https://docs.rs/glium/latest/glium/trait.CapabilitiesSource.html#tymethod.get_capabilities