Add exact text semantic reference and oracle - #34
Draft
isomorphisms wants to merge 4 commits into
Draft
Conversation
6 tasks
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.
Summary
contains_string, overlapping zero-based charactermatch_positions, andmatch_countWhy this slice first
PR #9 described a future grep-like extraction pass but did not implement one. This makes that ordinary-text operation real without prematurely baking an ARM trick into browser semantics.
The current ARM/Thumb backend is still straight-line and numerical; PR #8 is a branch/dispatch acceptance-spec change, not string/loop lowering. The browser oracle therefore lands as a separate slice. Target-specific work remains tracked in
isomorphisms/Idric#21andisomorphisms/idric-arm-thumb#9,#10, and#11.Semantics
Charsubstring matchingThe first ARM comparison should use ASCII fixtures so byte and character offsets coincide. Any later Unicode-optimized API must state its offset units explicitly.
Refs #33.