Add the MEOS.NET pin manifest and per-binding generator policy#6
Open
estebanzimanyi wants to merge 1 commit into
Open
Add the MEOS.NET pin manifest and per-binding generator policy#6estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
main still ships the regex MEOS.NET.Builder; the codegen-driven 1.4 surface lives in open PRs. Add tools/pin/compose-order.txt (the canonical fold manifest with the disposition of every open PR; MobilityDB#5 is the verified frontier containing MobilityDB#4) and GENERATION.md (the per-binding generator policy: MEOS.NET owns its generator in-repo at tools/codegen.py emitting the P/Invoke layer; the regex Builder is retired generate-then-retire).
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
ae2b442 to
544767f
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 MEOS.NET onto the ecosystem-wide per-binding generator policy (same treatment as JMEOS #29 and GoMEOS #6):
tools/pin/compose-order.txt— MEOS.NET's canonical, dependency-ordered fold manifest.mainstill ships the regexMEOS.NET.Builder; the codegen-driven 1.4 surface lives in open PRs. This file fixes the composing set/order and records the disposition of every open PR.GENERATION.md— the per-binding generator policy: MEOS.NET owns its generator in-repo attools/codegen.py(emitsMEOS.NET/Internal/MEOSExternalFunctions.cs+MEOSExposedFunctions.cs); the single source of truth is the MEOS-API catalog; the regex Builder is retired generate-then-retire (the last green-CI version is the equivalence probe).Docs + manifest only — no code, no build impact.
Disposition of the open PRs (committer review)
Verified ancestry (
git merge-base, this turn): #5 is the frontier (8 commits overmain) and contains #4.work/portable-aliasesbump/meos-1.4bump/meos-1.3-via-meos-idl.github/workflowsCI commit → forward-port #3's CI workflow onto the frontier, then close #3Why
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.