Skip to content

Track OverPy null-initializer default semantics #58

Description

@Teakowa

Goal: match pinned OverPy declaration-initializer behavior for null, 0, and 0.0.

Context: PR #54 / Issue #46 intentionally leaves this outside the bounded primitive slice. The current compiler suppresses only textual numeric 0; null is still emitted as an initializer.

Scope: add minimized pinned-oracle cases and the smallest source-attributed opy-rs lowering change.

Non-goals: no nonzero initializer changes, Workshop catalog changes, or #47 control flow.

Acceptance: all three spellings have oracle-backed behavior; frontend -> HIR -> compiler -> workshop-rs matches; 0.0 remains distinct from integer 0.

Follow-up from #54 review; not part of #46 completion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions