Revert encode_to_fmt API change

[jkczyz]

Maintaining the original error type allows for making a minor release since it won't break the API. This lets indirect consumers of the crate through rust-bitcoin's module re-export to use new functions (e.g., encode_without_checksum) without a new rust-bitcoin release.

[jkczyz]

Should this be merged into master and later reverted? Or into a separate release branch?

[apoelstra]

I think we should just merge into master and later revert it. No need for extra process for such a low-activity crate.

[apoelstra]

Can you rebase now that #76 is merged?

[apoelstra]

ACK 3693935

[apoelstra]

If you add a commit which bumps the minor version number I can publish a release right after merging.

[apoelstra]

ACK 0d01fad

[apoelstra]

Thanks! Tagged, signed and published.

[jkczyz]

Thanks! Tagged, signed and published.

Thanks for the quick turnaround on this! I had to add an explicit dependency in our crate otherwise I'd still get 0.9.0 from rust-bitcoin even after a cargo clean. But no conflicting definitions this time.

[apoelstra]

Did you try cargo update?

[jkczyz]

Ah, right. 😅 Forgot the Cargo.lock file dictates which version is used. Works without the explicit dependency.