Neovide crashes when both x & y blur are set to 0 #1707
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TENX-S
pushed a commit
to TENX-S/neovide
that referenced
this pull request
Jan 24, 2023
TENX-S
pushed a commit
to TENX-S/neovide
that referenced
this pull request
Jan 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
blur()returnNoneif both x & y blur are 0. I couldn't find any doc on this but I assume this is because a sigma of 0 makes a division by 0 error. Instead of crashing straight away viaunwrap(), it now simply does nothing (i.e. doesn't blur) ifNoneis returned.None.Did this PR introduce a breaking change?
A breaking change includes anything that breaks backwards compatibility either at compile or run time.