You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should unify our use of "indices" and "indexes"; presently, we use these effectively interchangeably around the codebase, but this has led to some inconsistent naming of types/information in documentation. Similarly, any types/functions we rename that existed in the previous release should have a second copy with the original name (e.g. a pub type for types, pub fn that calls the intended function for functions) and a #[deprecated] tag explaining the change.
This should preferably be completed after #1886 is merged.
The text was updated successfully, but these errors were encountered:
cc @domenukk@andreafioraldi@tokatoka: do we prefer "indices" or "indexes"? They are both valid; "indices" is primarily used in mathematical contexts, "indexes" for other fields.
See conversation below; we want to unify on "indexes".
We should unify our use of "indices" and "indexes"; presently, we use these effectively interchangeably around the codebase, but this has led to some inconsistent naming of types/information in documentation. Similarly, any types/functions we rename that existed in the previous release should have a second copy with the original name (e.g. a
pub type
for types,pub fn
that calls the intended function for functions) and a#[deprecated]
tag explaining the change.This should preferably be completed after #1886 is merged.
The text was updated successfully, but these errors were encountered: