Repository navigation
proposals: own schemas through relative paths, provenance, dependency groups, import formatting (draft) - #178
Merged
Merged
Conversation
…groups, import formatting (draft) Four pages under proposals/use-paths-and-groups: own schemas reached only through package::, parent:: and self:: (by edition), provenance recorded per compiled schema instead of inferred from namespaces (an IR format change), an optional group field on dependency entries that is presentation only, and a default import order configurable in a [format] table. Related to core#277 and core#268.
Kinflou
marked this pull request as ready for review
November 14, 2026 22:00
This was referenced Nov 14, 2026
Open
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
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.
A draft proposal, for review: how a
usepath says where a schema comes from, and how a package's dependencies are organised. Four pages underproposals/use-paths-and-groups/, linked from the proposals index and the nav like the other drafts.package::…,parent::…,self::…; an absolute first segment is alwaysstdor a dependency. Introduced by an edition: a warning with a language-server quick fix now, an error in the next edition.parentstays, nosuper. Reserved dependency names:std,package,parent,self.std) in the frozen IR, the generation request and the facts. An IR format change under core#268.groupon a dependency entry; the table stays flat; presentation only, excluded from every hash, pin and diff.deps add/deps pintake--group.std, the package's own, then dependencies by group (first-declared), alphabetical within a tier; a[format]table.Open questions (in the index page): the IR format for provenance (with format 4 or right after), where
[format]lives (recommendation:comline.toml), a per-user override, whether groups can orderstd, the edition number for the error, and one raised while drafting: what the shadowing guard becomes once provenance exists (two schemas can still land on one compiled namespace).Related: core#277, core#268. No issues created.