-
Just a thought - I think most of the arrays packages are named "*Arrays.jl" with an % cd .julia/registries/General
% rg Arrays.jl | wc -l
94
% rg Array.jl | wc -l
3 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Good point. When developing something that crosses two worlds, though, it's inevitable that we'll run into situations in which following one world's conventions means breaking another's. The Python package is named "Awkward Array" (singular), so naming this package AwkwardArrays.jl could cause some people to not be able to find it. I don't think there's a similar constraint from Julia: the singular may be unusual, but no one will be searching for this by taking an existing name and substituting a different adjective before "Arrays.jl". A similar collision of conventions happened in dask-awkward: we like to name Awkward extensions with "Awkward" as the first word (like awkward-pandas) because it's an adjective, but Dask extensions start with "Dask". Sometimes, I'm looking for "awkward-dask" and don't find it until I remember this. I'm going to move this to a Discussion, though. |
Beta Was this translation helpful? Give feedback.
Good point. When developing something that crosses two worlds, though, it's inevitable that we'll run into situations in which following one world's conventions means breaking another's. The Python package is named "Awkward Array" (singular), so naming this package AwkwardArrays.jl could cause some people to not be able to find it. I don't think there's a similar constraint from Julia: the singular may be unusual, but no one will be searching for this by taking an existing name and substituting a different adjective before "Arrays.jl".
A similar collision of conventions happened in dask-awkward: we like to name Awkward extensions with "Awkward" as the first word (like awkward-pandas) beca…