Follow the MEOS surface for the temporal subtype transforms - #17
Merged
estebanzimanyi merged 1 commit intoAug 31, 2026
Merged
Conversation
The catalog and the surface projected from it come from MobilityDB 2819428711. Selecting a temporal value's instant, sequence or sequenceset representation is a subtype transform rather than a cast, so MEOS names those three `temporal_as_*`; the hand-written temporal class still imported and called `temporal_to_*`, the spelling MobilityDB retired on 2026-07-17. Nothing reported it. The type-check regenerates the surface from the catalog in the tree, and that catalog was frozen at 4239d7bbc, so it kept publishing the old names and the call sites kept resolving against them. A binding type-checks against whatever surface it carries, which is why a catalog derived from master is what makes this class of drift visible at all. The three signatures are unchanged — `temporal_as_tinstant(temp)`, `temporal_as_tsequence(temp, interp)`, `temporal_as_tsequenceset(temp, interp)` — so the call sites take the names and nothing else. `npx tsc --noEmit` exits 0. The WASM build still fails, on wrappers the generator emits for functions the preamble does not declare and for a family the image does not build; both come from the generator's hand-maintained header and family lists, and are fixed where those lists are.
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.
The catalog and the surface projected from it come from MobilityDB
2819428711. Selecting a temporal value's instant, sequence or sequenceset
representation is a subtype transform rather than a cast, so MEOS names those
three
temporal_as_*; the hand-written temporal class still imported and calledtemporal_to_*, the spelling MobilityDB retired on 2026-07-17.Nothing reported it. The type-check regenerates the surface from the catalog in
the tree, and that catalog was frozen at 4239d7bbc, so it kept publishing the old
names and the call sites kept resolving against them. A binding type-checks
against whatever surface it carries, which is why a catalog derived from master
is what makes this class of drift visible at all.
The three signatures are unchanged —
temporal_as_tinstant(temp),temporal_as_tsequence(temp, interp),temporal_as_tsequenceset(temp, interp)—so the call sites take the names and nothing else.
npx tsc --noEmitexits 0. The WASM build still fails, on wrappers thegenerator emits for functions the preamble does not declare and for a family the
image does not build; both come from the generator's hand-maintained header and
family lists, and are fixed where those lists are.