You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Wrapper-planning errors and support claims |`x2py/semantics/policy_completion.py`, `x2py/wrapper_codegen/planner.py`|`docs/user/reference/diagnostic-codes.md`, `docs/user/language-support/feature-matrix.md`|`tests/semantics/policy/`, `tests/wrapper_codegen/`|
-[How do I keep Python's Global Interpreter Lock (GIL) during a call, or return to the normal releasing behavior?](calls-and-results.md#keep-the-gil-when-required)
75
75
-[How do I describe a callback signature in the contract?](../../guide/callbacks.md#choosing-the-prototype-spelling)
76
76
77
-
### Storage and Lifetimes
78
-
79
-
-[How do I understand or edit a complete ownership rule?](ownership-and-lifetimes.md#the-complete-ownership-rule)
80
-
-[How do I choose a value, copy, view, existing object, or new handle?](ownership-and-lifetimes.md#transfer-values)
81
-
-[How do I decide who releases persistent storage?](ownership-and-lifetimes.md#destruction-values)
82
-
-[How do I understand allocatable or pointer handle ownership?](ownership-and-lifetimes.md#common-handle-cases)
83
-
-[Why is an ownership combination rejected?](ownership-and-lifetimes.md#combinations-that-are-rejected)
84
-
85
77
Most edits change the Python surface: names, visibility, grouping, or how
86
78
native arguments appear as Python parameters and results.
0 commit comments