Skip to content

tracking: leftovers from the invariant/complexity refactor #1947

Open
4 of 14 issues completed
Open

Description

@shunichironomura

Warning

This content was written by an AI agent and must be verified by a human developer. After human verification, this alert may be removed.

Summary

Umbrella for the items intentionally left out of the invariant/complexity refactor (P0–P10), its handle-redesign follow-up (S0–S15), and the final sweep (#1934, #1935, #1937, #1938, #1939). Each was skipped because doing it then would have needed a language-design decision, a change to a type's identity, a new pipeline stage, or an evaluator-kernel redesign, not because it is unimportant.

Correctness and user-visible

Invariants still relying on callers or name lookups

Evaluator kernel

Public surface and small cleanups

Deliberately not tracked

  • Splitting the compiler crate (P10-4): decided against.
  • Boundary strings (time-zone spelling, rendered runtime values, WASM import names, wasmtime error text), the host-ABI array-rank check, and internal errors kept as boundary, construction-point or defence-in-depth checks. These are genuine boundary data or checks.

The internal_error_calls metric in internals/refactor-metrics.nu tracks progress; most items below should lower it.

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions