Added general error code enum when STBI_NO_FAILURE_STRINGS is defined #1600
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
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.
I thought it would be useful to have an error code enum in the case that STBI_NO_FAILURE_STRINGS is defined. In my case, I did not want to compile all of the strings but I still wanted to provide general feedback on failure types. Using an enum has the added benefit of allowing users to switch on the error and possibly provide their own failure reason strings.
I tried to keep the changes as unintrusive as possible. If I need to change or revise anything or if anyone has any suggestions for improvements please let me know!