Skip to content

compose-order: function shape is generated from headers#26

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:fix/manifest-shape-metadata-superseded
Jul 7, 2026
Merged

compose-order: function shape is generated from headers#26
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:fix/manifest-shape-metadata-superseded

Conversation

@estebanzimanyi

@estebanzimanyi estebanzimanyi commented Jun 28, 2026

Copy link
Copy Markdown
Member

The tools/pin/compose-order.txt manifest lists function-shape metadata — arrayReturn, outputArrays, and nullable — as generated from the C signatures and Doxygen by parser/shapeinfer.py and parser/nullable.py, covering every function. meta/meos-meta.json provides an override layer on top of the inferred baseline.

Manifest-only change; no build impact.

The compose-order manifest lists function-shape metadata (arrayReturn/outputArrays/nullable) as generated from the C signatures and Doxygen by parser/shapeinfer.py and parser/nullable.py. meta/meos-meta.json is an override layer on top of the inferred baseline.
@estebanzimanyi estebanzimanyi force-pushed the fix/manifest-shape-metadata-superseded branch from ef68e14 to cf01477 Compare July 7, 2026 08:43
@estebanzimanyi estebanzimanyi changed the title compose-order: drop the closed #2, keep the generated shape (#16) compose-order: function shape is generated from headers Jul 7, 2026
@estebanzimanyi estebanzimanyi merged commit abcbe61 into MobilityDB:master Jul 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant