Use imports public types

Platform spec ADR

Use imports public types

Back to Resolver contract ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Resolver contract - Contracts and edge cases Normative resolver guarantees including SymbolRegistry invariants and cross-unit reference matching. article Standard Reviewed Fri Jun 05
• Resolver contract - Design model Persistent resolver entities including SymbolRegistry, ItemId, and cross-unit identity. article Standard Reviewed Fri Jun 05
• Resolver contract - Examples Concrete symbol identity and cross-unit reference scenarios. article Standard Reviewed Fri Jun 05
• Resolver contract - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks. article Standard
• Resolver contract - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation. article Standard
• Resolver contract - Verification and traceability Tests and code anchors proving SymbolRegistry and cross-unit reference behavior. article Standard Reviewed Fri Jun 05

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 2 H2 heading(s)

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Resolver contract

  Parent feature hub

• Feature
  Program assembly

  Cross-module paths for use targets

Context

use Core.Results registered module aliases for member completion (IO.PrintLine) but did not import public types or enum constructors into unqualified value/type scope—breaking patterns such as Result::Ok after use Core.Results.

Decision

When resolving use Logical.Module.Path (with optional as Alias):

Binding	Rule
Module alias	Existing module_imports behavior for qualified member access remains
Public types	Each public type exported from the target module must bind in type scope under its simple name (or alias)
Enum constructors	Each public enum constructor must bind in value scope as Type::Variant and, when the type name is in scope, as unqualified constructor names per language-meta visibility rules
Non-public items	Must not be introduced into scope via use

Consequences

Resolver and items.rs grow use-import registration beyond alias tables. Analysis fixtures cover Core.Results / Result::Ok patterns.

Verification anchors

• compiler/crates/beskid_analysis/src/resolve/resolver.rs
• compiler/crates/beskid_analysis/src/resolve/items.rs
• compiler/crates/beskid_tests/src/analysis/resolve.rs
• compiler/corelib/beskid_corelib/tests/corelib_tests/src/core/ResultsTests.bd