Having lots of bytecode in a single contract is fairly costly; I'm thinking it will be ideal to have a contract for each type we want to support and link them together in some master contract for ease of use. Alternatively they could each live as a separate library on-chain, although I can see that being somewhat painful for end-users to navigate.
May also consider breaking up the actual functions if we end up with a lot of them, possibly exposing them like: Lambdeth.iterators.map() or Lambdeth.sort.quick().
Having lots of bytecode in a single contract is fairly costly; I'm thinking it will be ideal to have a contract for each type we want to support and link them together in some master contract for ease of use. Alternatively they could each live as a separate library on-chain, although I can see that being somewhat painful for end-users to navigate.
May also consider breaking up the actual functions if we end up with a lot of them, possibly exposing them like:
Lambdeth.iterators.map()
orLambdeth.sort.quick()
.