Verify authorized Swift Objective-C opaque model activation - #252
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.
Exercise the authorized Darwin/Foundation/Objective-C construction for the two opaque propagator templates with runtime fidelity and independent model-off/on controls. The declared model is load-bearing and respects the second-argument binding.
Key Changes:
Touch Points:
evidence/swift-opaque-objc-v1/scripts/*swift-opaque*.pydocs/swift-opaque-objc-prototype.md.github/workflows/ci.ymlValidation: 7 runtime tests and 9 activation/provenance tests,
cargo fmt --check, andgit diff --checkpass. The successful function-scoped extraction took 94.530s; all three queries and decodes completed under the 150s extraction / 60s query / 2048 MiB analysis request. Runtime selector evidence is distinct from static wrapper binding; no resolved dynamic perform target is claimed.Non-scored prototype only: no population registration, other-analyzer qualification, whole-profile qualification, freeze or publication. Aggregate memory compliance and semantic completeness remain unproven.
Refs #220 and #215. Both issues remain open; acceptance is incomplete.