Exclude L1 and L3 requirements from OFT check #188
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
sophokles73
added
enhancement
The L1 and L3 specifications contain requirements for implementations of the corresponding APIs and thus are not relevant for the Rust language library, which only defines these APIs but does not implement them. Note that the library contains a (default) implementation of the L2 API and thus still needs to cover the requirements specified for L2.
sophokles73
force-pushed
the
do_not_consider_utransport_requirements
branch
from
91308dd
to
5c4b8f7
Compare
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.
The L1 and L3 specifications contain requirements for implementations
of the corresponding APIs and thus are not relevant for the Rust
language library, which only defines these APIs but does not
implement them.
Note that the library contains a (default) implementation of the L2
API and thus still needs to cover the requirements specified for L2.