Cope with interfaces that are always v1 #44
Merged
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
Normally the child has the same version as the parent. But some interfaces don't follow this rule (wl_callback, wl_buffer, wl_region) and remain at v1 always.
talex5
added a commit
to talex5/opam-repository
that referenced
this pull request
Apr 5, 2024
CHANGES: - Add relative-pointer-v1 (@Mic92 talex5/ocaml-wayland#40). - Add pointer-constraints-unstable-v1 (@Mic92 talex5/ocaml-wayland#41). - Update protocols to latest versions (@talex5 talex5/ocaml-wayland#43). - Cope with interfaces that are always v1 (@talex5 talex5/ocaml-wayland#44).
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.
Normally the child has the same version as the parent. But some interfaces don't follow this rule (wl_callback, wl_buffer, wl_region) and remain at v1 always. Special-case that.