Skip to content

[core] Promote unexpected varying types to log::error. - #9982

Open
jimblandy wants to merge 1 commit into
gfx-rs:trunkfrom
jimblandy:core-clip-distances-validation-logging
Open

[core] Promote unexpected varying types to log::error.#9982
jimblandy wants to merge 1 commit into
gfx-rs:trunkfrom
jimblandy:core-clip-distances-validation-logging

Conversation

@jimblandy

Copy link
Copy Markdown
Member

When wgpu_core finds a binding with an unexpected type, log that with error severity, not debug. This was demoted to debug in be6898f, because, as the comment says:

every shader coming from glslc outputs an array of clip distances
and hits this path :(

However, #8762 added a match case above this that handles clip distance arrays, so such output should no longer trigger any logging at all.

cc: @ErichDonGubler

When `wgpu_core` finds a binding with an unexpected type, log that
with `error` severity, not `debug`. This was demoted to `debug` in
be6898f, because, as the comment says:

> every shader coming from `glslc` outputs an array of clip distances
> and hits this path :(

However, gfx-rs#8762 added a match case above this that handles clip
distance arrays, so such output should no longer trigger any logging
at all.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant