Add DefaultTracker

[KyrylR]

No description provided.

[KyrylR]

Though, I still have doubts regarding this

[apoelstra]

Overall this looks great. I have two comments in 1f7ef82:

• You use both custom sinks and eprintln calls. Maybe you should only call the sinks, and let the user make one that calls eprintln if they want stderr?
• You only handle the "successful jet" case. But I think the user probably cares more than anything about failed jets.

[KyrylR]

Overall this looks great. I have two comments in 1f7ef82:

* You use both custom sinks and `eprintln` calls. Maybe you should only call the sinks, and let the user make one that calls `eprintln` if they want stderr?

* You only handle the "successful jet" case. But I think the user probably cares more than anything about failed jets.

Good point, migrated to sinks, and here how it looks when jet fails:

[apoelstra]

ACK 74f8c06; successfully ran local tests

[KyrylR]

@apoelstra sorry, forgot to bump version

[apoelstra]

@KyrylR do you think I should cut a release immediately? If so, can you update CHANGELOG.md?

Based on

git log master --not simplicityhl-0.3.0 --first-parent --oneline

it looks like this is the only user-visible change to SimplicityHL.

[apoelstra]

ACK 813140b; successfully ran local tests

[KyrylR]

Merged and published. Thanks!

[apoelstra]

@KyrylR can you also make a git tag (git tag -as). See git tag for the current list and git show <tag> for the text added to each one. (Though the text doesn't matter, I think. I've never read this text, but git makes you put it in, so I usually just repeat the crate name.)

[KyrylR]

@apoelstra, Done: https://github.com/BlockstreamResearch/SimplicityHL/tags

[apoelstra]

Great, thanks!