no_std Compatibility

[mriise]

Waiting for #27 for me to keep sanity over changes.

fixes #24 thanks to work done by @whalelephant and @ia0 over in #25

This allows multibase to only require a global allocator in no_std environments.

[vmx]

I just merged #27. BTW, you want to mention @whalelephant instead :)

[mriise]

ah thanks, took glasses off for a minute and didnt bother to read the whole thing...

[mriise]

@vmx it might be good to add some info in README and adding 'no_std' to the cargo tags- things like that before merge.

[vmx]

I make this a "request changes" due to the git based dependency of the base-x-rs fork.

@mriise feel free to add the "no_std" tag as part of this PR.

[mriise]

@vmx after this PR could we get a no_std build target added to CI?

[vmx]

@vmx after this PR could we get a no_std build target added to CI?

Yes we should. I tried things locally and I think we should use the cargo build --target thumbv6m-none-eabi --no-default-feature trick (https://blog.dbrgn.ch/2019/12/24/testing-for-no-std-compatibility/). For me cargo nono doesn't report it properly, it even doesn't return an error if I compile with the std feature enabled.

[mriise]

Like this?

[vmx]

The rest looks good!

[mriise]

There we go

[vmx]

Thanks for the hard work and fighting CI!