feat: openkal 0.2.0 and openkal-linux 0.2.0 — the specification owns the interface - #221
Merged
Conversation
The specification now owns the interface. Version 0.1 placed the module a
consumer imports under the control of the implementation: the specification
package provided openkal.decl.<name> and the implementation re-exported it as
openkal.<name>. That contradicts what a specification is for, and it made the
name a consumer relies upon the property of a party the specification does not
govern.
consumer --imports--> openkal <--imports-- implementation
| |
+------------ links against ---------------+
An implementation now contributes definitions and exports no module. It imports
the same interface a consumer imports, because it needs the declarations it is
defining.
The earlier arrangement existed to support detection of optional operations
through argument-dependent lookup, which requires an implementation's
declarations to be visible to the consumer. Version 0.1 defined no optional
operation, so the mechanism served nothing that existed, and clause 6.3 now
records the alternatives and the measurements that constrain them.
0.1.0 is replaced rather than retained. Two incompatible specifications under
one name would be worse than the absence of the earlier one, which no project
uses.
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
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.
The specification now owns the interface. Version 0.1 placed the module a
consumer imports under the control of the implementation: the specification
package provided openkal.decl. and the implementation re-exported it as
openkal.. That contradicts what a specification is for, and it made the
name a consumer relies upon the property of a party the specification does not
govern.
An implementation now contributes definitions and exports no module. It imports
the same interface a consumer imports, because it needs the declarations it is
defining.
The earlier arrangement existed to support detection of optional operations
through argument-dependent lookup, which requires an implementation's
declarations to be visible to the consumer. Version 0.1 defined no optional
operation, so the mechanism served nothing that existed, and clause 6.3 now
records the alternatives and the measurements that constrain them.
0.1.0 is replaced rather than retained. Two incompatible specifications under
one name would be worse than the absence of the earlier one, which no project
uses.