Conversation
… dont mix the plans that are dedicated to bridge to binding and vice versa
…ent and compare with f2py --no-wrapper
…ent and compare with f2py --no-wrapper
…ent and compare with f2py --no-wrapper
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
+ objects by their inspected symbol relationships across f2py build backends
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.
bind(C)calls and the initial direct-only C wrapper backend, includingconservative starter-contract defaults for ambiguous C pointers.
@native_abi("c")to semantic.pyicontracts so Fortranbind(C)procedures retain their ABI and optional link label through generated and
source-free contract workflows.
cohort with untimed correctness, generated-source membership, and linked
direct-symbol preflight, plus an ordinary-Fortran PRIK control.