bump major version for backwards-incompatible breaking change

[warrenguy]

Regarding https://github.com/govalues/decimal/releases/tag/v0.1.34

I understand this module is v0 but please consider bumping the major version anyway. This is a very significant behavioural change that is not backwards-compatible and will break badly for anyone who has used the binary marshaler interface.

[eapenkin]

Dear @warrenguy,

I am sorry that the changes in v0.1.34 caused problems. To fix this, I will make the old binary functions (BCD functions) publicly available in v0.1.35, but mark them as deprecated. This allows people to use them for a bit longer. I will remove them completely in v1, which will be ready in a few weeks.

Is this okay as a temporary fix?

[warrenguy]

Hi @eapenkin, no problems at all.

Is there a reason not to keep the BCD functions around? They're far more space-efficient and about three times faster to encode. I'm happy to fork if you opt not to keep them around, and I understand move to strings for default encoding, but I just wonder if there is a fundamental problem I am missing.

FYI I raised #58 earlier to restore the functions

[eapenkin]

They're far more space-efficient and about three times faster to encode.

That's exactly why I added it initially. The only issue is that some DB drivers (like Redis) mix binary and text methods. I think that interoperability is more important than performance here.