Talk about interface about buffet

[Drup]

What's the goal here ? Do you really want to be able to get values that can be dynamically be string/bytes/bigstrings, or do you want to be able to write your encoding/decoding algorithms on various structures easily ?

The current version is ridiculously full of indirections, to the point where you will seriously hurt performances. Using module abstractions, with various signatures that correspond to the various features, would allow you to keep indirections to a minimum.

[dinosaure]

I would like to have an abstraction between bigstring/string and bytes and choose which one I use it dynamically. This is the main purpose of this library where sometimes I would like to use string instead bigstring.

I agree about indirection and the bottleneck is about the dispatch between kind of buffers.

It seems interesting to provide Buffet3 feature (slice) directly over Buffet0 and implement capabilities with polymorphic variants over Buffet0 too.

I will try to provide signatures for each feature and see what happen.

[dinosaure]

We can more precisely talk about performances issues with benchmark/benchmark.ml now and bechamel. I will make some tests step by step and print results here.