Skip to content

Refactor FFI guard and SIMD scalar implementations#649

Closed
seuros wants to merge 1 commit into
dmtrKovalenko:mainfrom
seuros:refactor/dedup-round-2
Closed

Refactor FFI guard and SIMD scalar implementations#649
seuros wants to merge 1 commit into
dmtrKovalenko:mainfrom
seuros:refactor/dedup-round-2

Conversation

@seuros

@seuros seuros commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

The repeated handle/lock/init matches in fff-c collapse into try_inst!/try_cstr!/read_picker! macros, and the free/accessor bodies share free_array/elem_at helpers.

The NEON and AVX2 memmem kernels now share one packed_pair_tail and verify_scalar_from.

Also i drops the stale fff-core copy of parse_bench.rs left behind by the query-parser crate extraction.

1 duplicate file removed.

No logic was modified

The repeated handle/lock/init matches in fff-c collapse into
try_inst!/try_cstr!/read_picker! macros, and the free/accessor bodies
share free_array/elem_at helpers. The NEON and AVX2 memmem kernels now
share one packed_pair_tail and verify_scalar_from. Also drops the stale
fff-core copy of parse_bench.rs left behind by the query-parser crate
extraction. Exported C symbols and header unchanged.
@seuros seuros force-pushed the refactor/dedup-round-2 branch from 6830af1 to 8287aec Compare July 5, 2026 12:40
@seuros

seuros commented Jul 5, 2026

Copy link
Copy Markdown
Contributor Author

seem like flacky windows tests (i dont test in windows). But the PR is just code restructured so the failing test are order dependant. fixed in #644

@dmtrKovalenko

Copy link
Copy Markdown
Owner

I appreciate your initiative but I am not a fan of custom propitiatory macros - it is hard to understand what the code is doing when it is hidden behind the macro, so for this kind of 5-10 lines duplications I prefer copy-pasting the code especially given the fact that AI today does this pretty well

1 similar comment
@dmtrKovalenko

Copy link
Copy Markdown
Owner

I appreciate your initiative but I am not a fan of custom propitiatory macros - it is hard to understand what the code is doing when it is hidden behind the macro, so for this kind of 5-10 lines duplications I prefer copy-pasting the code especially given the fact that AI today does this pretty well

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.

2 participants