Skip to content

Emitter abstraction layer: decouple language semantics from Python backend #147

@Mnehmos

Description

@Mnehmos

Problem

NLS language semantics are currently entangled with Python emitter quirks. The 'language' is effectively a Python macro system, not an independent language with its own semantics.

Acceptance Criteria

  • Defined IR (intermediate representation) between parser/resolver and emitters
  • Python emitter consumes IR, not raw AST
  • TS and Rust emitters (feat: TypeScript target #20, feat: Rust target #24) also consume same IR
  • Language spec can be validated against IR independently of any backend
  • Emitter plugins can be authored without touching core parser/resolver

Why This Blocks v1.0

A production language platform must be separable from its implementation backend. This is the architectural gate for multi-target and long-term language stability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    coreCore language semantics and designemitterCode generation targetspriority-highImportant, address soon

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions