Robin Freyler

Initial implementation of `Binary`, `LowerHex` and `UpperHex` in https://github.com/Robbepop/apint/commit/edf46b111c410b1643000ba162bddf95e43c707c and forwarding impls for `Int` and `UInt` in https://github.com/Robbepop/apint/commit/af6d35bf2f0dd0952e24af60817d4f0ee1e9399c. Now only the implementation for `Octal` is missing.

Hey, thank you for this! You are totally right. Can you make a pull request? I would be very glad to merge it. Did not know anyone would plan to...

> > > Thanks for writing this up! I'll add this to the agenda for discussion in the [next meeting](https://github.com/WebAssembly/meetings/blob/master/2020/CG-01-21.md). If you are a CG member, feel free to join...

Rewriting the constbv library is a major undertaking but considering the licensing problem it really should be done ... or STP should ideally build on another already existing constbv library....

+1 and thanks apasel422 for linking my PR and pointing me to this RFC! ;)

There is a lot more tied to the decision to entirely disregard state rent for ink!. For example, we will need a partial rewrite of our storage infrastructure and traits...

Okay, so state rent removal is pretty much set into stone from what this reads. If that's the case we will require some ink! adjustments as well that go well...

I thought about it for a moment. Maybe it makes sense to create a project to have a platform where we can discuss what needs to be done for ink!...

In the past we were overly restrictive with respect to checks like the one mentioned in this issue. I currently see no reason why we should not allow `mut` specifier...

The special challenge behind this is to find a solution that optimally works without using heap memory allocation so that simpler contracts can still get rid of the heap allocator....