Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue: Converting error representations #1134

HeroicKatora opened this issue Feb 7, 2020 · 0 comments

Tracking issue: Converting error representations #1134

HeroicKatora opened this issue Feb 7, 2020 · 0 comments


Copy link

@HeroicKatora HeroicKatora commented Feb 7, 2020

The 0.23 brought a more detailed and strictly typed error representation. We kept an internal compatibility interface here to reduce the rework effort required. The plan is to incrementally port these to use more of the new, shiny features. For a basic example, see the png module. To help, claim one of the image formats by a dedicated tracking PR or issue and rework its decoder and encoder implementation or claim a legacy constructors and deprecate and remove it.



  • InsufficientMemory
  • DimensionError
  • ImageEnd: #1142
  • UnsupportedError(String)
  • UnsupportedColor(ExtendedColorType)
  • FormatError(String)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Version 0.23
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.