Refactor withdrawMultiple to in include block.timestamp

[smol-ninja]

Motivation

• An array of time cannot trigger a full withdrawal due to unpredictability of block.timestamp
• That means, it wouldn't work if the intent is to withdraw the "full" amount from multiple streams which imo is going to be more common.

That is why I suggest to remove uint40[] calldata times from it and use block.timestamp instead.

function withdrawMultiple(uint256[] calldata streamIds) external;

instead of

function withdrawMultiple(uint256[] calldata streamIds, uint40[] calldata times) external;

Side note: If a user intents to include time in withdrawMultiple, they can do it programatically using withdraw function.

[andreivladbrg]

An array of time cannot trigger a full withdrawal due to unpredictability of block.timestamp

i don't think i understand this point

---

why don't we add withdrawMaxMultiple instead and keep:

function withdrawMultiple(uint256[] calldata streamIds, uint40[] calldata times) external;

[smol-ninja]

i don't think i understand this point

By passing time value as the current time, there will be a residual amount left in the stream proportional to block.timestamp - inputTime.

why don't we add withdrawMaxMultiple instead and keep

The most useful functions will be called withdrawMax and withdrawMaxMultiple. I was suggesting to call the most useful functions as withdraw and withdrawMultiple.

[smol-ninja]

We agree to define a new function called withdrawMaxMultiple.

[smol-ninja]

Issue created:

• Implement withdrawMaxMultiple #73