The test compiles and runs without notices/warnings/errors.
Note: this is a breaking change, since many APIs were updated to
return !int instead of ?int, since they do return errors,
and soon the old ?int return type will be only able to
return Options (i.e. none | Type), and not Results (error | Type).
The rest of the changes here are cosmetic (v fmt -w . + fixing deprecation notices about err.msg -> err.msg() ).
Hello. Is this PR will be merged soon or should I ignore this? I'm thinking about working on this package and since these are breaking changes I'd appreciate it if I can get an answer.
The test compiles and runs without notices/warnings/errors.
Note: this is a breaking change, since many APIs were updated to return
!int
instead of?int
, since they do return errors, and soon the old?int
return type will be only able to return Options (i.e. none | Type), and not Results (error | Type).The rest of the changes here are cosmetic (
v fmt -w .
+ fixing deprecation notices abouterr.msg
->err.msg()
).