I’ve generally been on the “let the NumPy devs worry about it” side of things,
but I do agree with Ilhan that `like=` is confusing and `typeof=` would be a
much more appropriate name for that parameter.
I do think library writers are NumPy users and so I wouldn’t really make that
distinction, t
For what is worth, as a potential consumer in SciPy, it really doesn't say
anything (both in NEP and the PR) about how the regular users of NumPy will
benefit from this. If only and only 3rd parties are going to benefit from
it, I am not sure adding a new keyword to an already confusing function is
