Use warn_once
where relevant instead of manually implementing a single warn check
#11693
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
bool
/AtomicBool
to warn once.Solution
warn_once
macro which internally creates anAtomicBool
.Downside: in some case the warning state would have been reset after recreating the struct carrying the warn state, whereas now it will always warn only once per program run (For example, if all
MeshPipeline
s are dropped or theWorld
is recreated forLocal<bool>
/ abool
resource, which shouldn't happen over the course of a standardApp
run).Changelog
Removed
FontAtlasWarning
has been removed, but the corresponding warning is still emitted.