Added a safer constructor for Image #637
Open
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
|
Just jumping in here since I encountered issues with image manipulation for a small project: We probably want to check overflows of usize type here. see for instance https://docs.rs/image/latest/src/image/buffer.rs.html#1271 |
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.
This PR is the solution to issue #634.
I've added a new constructor
Image::new(width, height) -> Image, which abstracts away the process of making a new image, making it less error prone. Having to manually manage the amount of bytes needed was unnecessary and inefficient.This is my first ever pull request so let me know if i missed anything or need to improve on anything.