Add the MobilityDuck pin manifest and per-binding generator policy#206
Open
estebanzimanyi wants to merge 1 commit into
Open
Add the MobilityDuck pin manifest and per-binding generator policy#206estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
Add tools/pin/compose-order.txt (the canonical fold manifest of the 30 open PRs, derived from the live base<-head DAG and organized into dependency waves) and GENERATION.md (the per-binding generator policy: MobilityDuck's hand-written UDFs converge on a catalog-driven generator, tools/codegen_duck_udfs.py, via generate-then-retire; the hand feature PRs dissolve as generation lands).
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
3e1d58d to
d107b03
Compare
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
1 participant
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.
What
Brings MobilityDuck onto the ecosystem-wide per-binding generator policy (same treatment as JMEOS #29, GoMEOS #6, MEOS.NET #6, meos-rs #4, PyMEOS #96, PyMEOS-CFFI #21):
tools/pin/compose-order.txt— the canonical, dependency-ordered fold manifest of the 30 open PRs, derived from the livebase<-headDAG and organized into dependency waves (pin foundation → extended types → parity → geography → features → multi-version/CI → diagnostics → docs → benchmark). Ends the moving-target backlog.GENERATION.md— the per-binding generator policy + MobilityDuck's canonical target: generate the DuckDB scalar UDFs frommeos-idl.jsonvia an in-repotools/codegen_duck_udfs.py(organized by@ingroup, family-gated, BLOB marshalling), replacing the hand-written UDFs generate-then-retire.Docs + manifest only — no code, no build impact.
Notes for review
main(the catalog generator is the planned migration, not yet landed). As generation lands andgenerated ⊇ handis proven family-by-family (parity-audit + sqllogictest + BerlinMOD), most of the hand feature PRs in the manifest are mooted.#150→#156, parity#193→#201) fold base-before-head per the live DAG; the pin-bump PRs (#197/#200/#203/#204) are pin mechanics, folded once to the latest ecosystem pin at assembly.Why
Per the per-binding generator policy: each binding owns its generator + its own pin manifest, the single source of truth is the MEOS-API catalog, and generation converges to a zero-hand-written surface via generate-then-retire.