Forking ipfs/js-ipfs#3252 (comment) into separate issue.

Looks like some of our API calls return values that refer to same ArrayBuffer, which in turn causes one of the encoder functions https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-message-port-protocol/src to add it to the transfer list twice and error on postMessage.

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

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

all of the cors_catch wrapper stuff should be moved to http_request_expansion

Example
https://github.com/Anniepoo/identity/blob/master/prolog/identity/identity.pl

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]