Skip to content

Decide the bytes return of a MEOS byte buffer where the wrapper is built - #44

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:gen/bytes-in-wrapper-builder
Oct 31, 2026
Merged

estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:gen/bytes-in-wrapper-builder

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

build_function_string returns a single bytes object for a function whose
return is uint8_t * and whose one output parameter is a size_t *, reading
the two types it builds the wrapper from, as apply_input_arrays takes a
uint8_t input array as bytes. The text modifier that rewrote each generated
wrapper of that shape after the fact, byte_array_modifier, and the catalog
lookup that selected it are removed.

Measured: from one catalog of MobilityDB master b3be2105fd, the generator
writes functions.py and init.py byte for byte as before, the 48 byte
buffer functions returning bytes.

build_function_string returns a single bytes object for a function whose
return is uint8_t * and whose one output parameter is a size_t *, reading
the two types it builds the wrapper from, as apply_input_arrays takes a
uint8_t input array as bytes. The text modifier that rewrote each generated
wrapper of that shape after the fact, byte_array_modifier, and the catalog
lookup that selected it are removed.

Measured: from one catalog of MobilityDB master b3be2105fd, the generator
writes functions.py and __init__.py byte for byte as before, the 48 byte
buffer functions returning bytes.
@estebanzimanyi
estebanzimanyi merged commit fd63bcc into MobilityDB:master Oct 31, 2026
4 checks 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