[proposal] make name of new/make function consistent about core HOT 2 OPEN

What could be the difference between T::new(...) (like Bytes::new(Int, ~initial)) and T::make(Int,T)?

Some mutable collections like Array, there are functions such as new(~capacity) and make(Int, T), Since function overloading is not allowed, they must have different names. For types that have only one new/make function, and the function type does not resemble f(Int, T) -> Self, f(Int, () -> T) -> Self, or f(Int, (Int) -> T) -> Self, I suggest using the name new to ensure that the IDE completion can always provide a "constructor" when the user types T::new.

I'd suggest we only keep

make -> T::make_with(Int,() -> T) and makei -> T::make_with_index(Int, (Int) -> T)

which is also analogous to map and mapi

The make(Int,T) and make(Int,() -> T) is difference because the elements of first one are physically equal.

from core.

What could be the difference between T::new(...) (like Bytes::new(Int, ~initial)) and T::make(Int,T)?

I'd suggest we only keep

make -> T::make_with(Int,() -> T)
and
makei -> T::make_with_index(Int, (Int) -> T)

which is also analogous to map and mapi

from core.