You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
May I suggest that with a released version there should be no stderr output either an appropriate returnResult or some function that allows the caller to read the error cause in case the read result (i.e. metadata) length is Zero, meaning that LittleExif did not find acceptable exif information.
Supposedly using a Result as return is not a good idea, as the user would like to use the new created Metadata struct (and hiding same in an Error type seems rather weird). Hence a function that returns the latest reason why metadata could not be decoded might be the most viable option.
May I suggest that with a released version there should be no
stderr
output either an appropriatereturn
Result
or some function that allows the caller to read the error cause in case the read result (i.e. metadata) length is Zero, meaning that LittleExif did not find acceptable exif information.Originally posted by @mschnell1 in #37 (comment)
The text was updated successfully, but these errors were encountered: