feat: add concrete application engines and bounded multidimensional indexes#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.
Summary
BoxIndex, fixedBoxIndex2D/3D/4Daxis-projection indexes, and guardedBoundedBoxIndexRangeSetpayload ownership, callback reentrancy, failure atomicity, and compatibility with the original three-method structuralPayloadPolicycontractRangeSetas the stable one-dimensional API; multidimensional types remain experimental namespace-only exportsValidation
just validate: 977 passed, 18 skipped; stable backends 30 passedjust check: 955 passed, 15 skipped, 25 deselected; 95.24% branch coveragejust run-examples: all 54 examples passed from/tmpgit archivewheel/sdist build, artifact-policy verification, and arbitrary-CWD clean-wheel install passedPlatform notes
Validated locally on macOS arm64 with Python 3.12. CUDA, Metal-device, Boost ICL, and the full cross-platform release matrix remain CI/hardware-lane responsibilities. Experimental accelerators are not automatically selectable stable backends.