Deleted/active recipients flag

[adria0]

Consider to add a flag active in struct Recipient(like struct Spender) instead using activationTime == 0 as deletion flag

[jbaylina]

It but it would take more gas...

[GriffGreen]

gas optimization is something I want to do some time on this contract... i don't know if its best done now or after the first run of tests.... but low gas is a huge priority... mostly cause i think I will end up using these contracts a lot and am very cheap ;-)

[dipenjoshi]

i'm mostly worried about out of gas exceptions. being cheap on gas is 2nd priority.

[GriffGreen]

I agree about the out of gas annoyances! This is something that mostly needs to be fixed in estimateGas() on the UI side, but it has been a big problem for us

[jbaylina]

Here, the discusion is about "gas optimization" <-> "code readability" .

[adria0]

Proposal:

• Finish tests (& fix code bugs)
• Make special tests only to check gas usage for specific scenarios (which ones?)
• Make proposals for "gas optimization" <-> "code readability" equilibrium. Check changes against gas tests and then decide.

[GriffGreen]

sounds good.