Repository navigation
Use builtin type annotations for registered declaration projection - #10
Merged
Merged
Conversation
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
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 added-line Ruff gate on merged #9 requires builtin
typeannotations. Correct the registered-pair return annotation totuple[tuple[type, type], ...]; the existing mapping and runtime projection remain unchanged.Validation: the local added-lines Ruff check passes. The preceding 25 factory and 119 OpenHCS consumer tests cover the unchanged behavior; all ObjectState CI runtime test platforms passed on #9. This is a style correction to the return annotation introduced in #9; the underlying readiness implementation is already on main.