Skip to content

feature - package-derived vocab helper bindings from public exports #759

Description

@dannymeijer

Summary

v0.6 implements the complete package-derived vocabulary-helper contract: a vocab companion emits checked package helper calls through the same public export surface that ordinary consumers use, with no duplicated Rust-side helper list.

Scope

  • Package-public helper discovery and validated namespaced helper-call artifacts.
  • Helper eligibility categories, aliases, facade reexports, source spellings, keyword-safe names, and deterministic duplicate/unknown/ineligible diagnostics.
  • Package-build validation, checked API metadata, package-consumer equivalence, backend-neutral lowering, documentation, and a real InQL migration.
  • Full fixture coverage for ordinary helpers, aliases, reexports, non-helper exports, keyword spellings, stale output, and failure modes.

Boundaries

  • No vocabulary-specific package registry, lexical bare-name authority, or generated-Rust helper list.
  • Participating packages may migrate incrementally, but the supported contract is complete.

Delivery

Done when

  • Participating vocab companions require no duplicated helper binding list.
  • Package metadata, diagnostics, and consumer behavior agree for every supported helper boundary.
  • InQL proves the contract in a non-synthetic package.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    RFCAdding or updating RFC documentsdocumentationImprovements or additions to documentationincan language semanticsSuggestions, features, or bugs related to the Incan Language itself (syntax and semantics)toolingSuggestions, features, or bugs related to the Tooling (CLI/formatter/test runner)

    Projects

    • Status
      Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions