Module stability 

Experimental standard-library items and the project’s opt-in to them (standard-library S3, #1963; track D2).

A first-party item (a unit, an exported item, or a capability operation, by dotted path) is stable or experimental. Using an experimental one needs an entry covering it under bynk.toml’s [unstable] allow. One StabilityPolicy per project carries that list and the experimental items, and both the build and the editor build it the same way (StabilityPolicy::for_project), so they never disagree about a file.

Structs

StabilityPolicy

A project’s stability policy: what is experimental, and what it allows.

UnitStability

The stability facts one unit’s checks need: the project’s policy, for the paths a check computes itself (a capability operation), and the unit’s imports that are blocked, by name, decided where provenance is known.

Constants

EXPERIMENTAL

The diagnostic for using an experimental item without opting in.

MANIFEST

The manifest the [unstable] diagnostics are attributed to.

NOT_EXPERIMENTAL

The warning for an [unstable] allow entry that reaches nothing experimental.

UNKNOWN_ITEM

The error for an [unstable] allow entry that names no first-party item.