Currently there is no possibility to set up a custom rounding function. Therefore you are limited to the ones that are implemented by default. For my case I need a rounding function that always rounds up (e.g. 0.002 => 0.01 with precision 2, commercial rounding)

It would be nice to pass a callback or a string that describes the rounding mode. If it is a string and the string matches the suppo

What happened
immuclient supports to query by transaction id
immuclient tx #

But the error messages are not clear or when the transactions id is invalid:
immuclient tx 0 returns illegal arguments, immuclient tx -0 tries to map it with a flag unknown shorthand flag

What you expected to happen
better error message would be `invalid TXid - transaction id range start with 1

Currently they wrap them into pvector which is not as efficient as it could be in Python 3.

Server giving commit id in the returned JSON when there are updates

This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:

• http/README.md has no tutorial on how to try out ipfs-http
• ipfs-http supports only `i

This operations will be used to drop elements in the steam on the right of the given element

var elements = []int{10,12,7,41,5,6}
res:=koazee.StreamOf(elements).DropRight(12).Out().Val()
fmt.Println(res)

// [10,12]