Skip to content

Remove naga's span and validate features #4705

Closed
@teoxoy

Description

It's unclear why the spans are gated behind the span feature. They are essential for diagnostics, take almost no space, and all users of naga that I could find enable it or have it enabled because they depend on wgpu-core transitively.

The validate feature might have more value than span as it gates quite a bit more code than span but still gets enabled by wgpu-core unconditionally.

The main driving factor behind removing them is maintenance burden (having to always consider the case where those are not enabled).

Related (original PRs):

Metadata

Assignees

No one assigned

    Labels

    kind: refactorMaking existing function faster or nicernagaShader Translator

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions