Roadmap 1.0

[tisonkun]

Before releasing 1.0, we'd agree on the major APIs.

For bounded pools, it seems all work well.

For unbounded pools, there are several considerations:

1. To support functionality like sync.Pool's New, shall we use the current Pool<T, M: ManageObject<Object = T>> solution, or use a Pool::get_or_create method to pass in the create fn.

Related projects:

• https://github.com/brettwooldridge/HikariCP
• https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing

[tisonkun]

or use a Pool::get_or_create

Or both? The pass-in function may be of AsyncFnOnce, then this change won't be a blocker but perhaps a follow-up add-on.

Implemented in #9.

[tisonkun]

Consider whether or not support minimal objects in bounded pool.

Maybe -

1. Try acquire permits (min_cnt.saturating_sub(pool.status().current_size))
2. Pop existing conns, on missing, create a new conn

Implemented in #14.

For unbounded pool, it can be easily implemented as:

let gap = mim_count.saturating_sub(pool.status().current_size);
// make minimum_objects with size <gap>
pool.extend(minimum_objects);

and we don't accurately manage size there.

[tisonkun]

Consider whether or not add retain method for unbounded pool.

This is done in #13.