Automatically initialise libvips by default #177
Merged
Conversation
This file contains hidden or 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
Contributor
|
LGTM! It's really the best solution I think, both from a "prevent users from doing the wrong thing" and a "keep the API simple and intuitive" perspective. README is great as well 👍🏾 |
lopcode
force-pushed
the
task/no-crash-when-not-inited
branch
from
2d8ce19 to
c8fbc10
Compare
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.
Follows from discussion in #176 - I realised we could do this with static initialisers.
cc @jbaiter - what do you think of the docs (the README specifically)? You can ignore the javadoc HTML junk, it added a new section to everything because there's a new deprecation warning.