Skip to content

Evaluate cost / benefit of "span" feature #4433

@jimblandy

Description

@jimblandy

The "span" feature is essential for producing usable diagnostics. As we improve Naga's diagnostics I suspect it's going to become harder to maintain "span" as an optional feature, as opposed to simply providing it by default.

We should measure the impact of the "span" feature on speed, memory consumption, and code size, and see what it would cost to simply enable it unconditionally.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: naga front-endTranslation to Naga IRkind: 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