[C++] Review compute function names

[asfimport]

We should probably make compute function naming more consistent while it's not too late.

Examples:

• "isin", "minmax" but "less_equal", "or_kleene", "binary_contains_exact"
• "binary_contains_exact" only works on string types
• "ascii_length" accepts non-ascii input and simply counts the number of bytes
• "partition_to_indices" vs. "NthToIndices"

Reporter: Antoine Pitrou / @pitrou
Assignee: Antoine Pitrou / @pitrou

Related issues:

• [C++][Doc] Undocumented compute functions (string_isalpha, etc.) (incorporates)

PRs and other links:

• GitHub Pull Request #7755
• GitHub Pull Request #7760
• GitHub Pull Request #7764

_{Note: This issue was originally created as ARROW-9390. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou:
Also, perhaps the "strptime" function should instead be a variant of "cast"?

[asfimport]

Kouhei Sutou / @kou:
Can we mark this as a blocker of 1.0.0?

[asfimport]

Antoine Pitrou / @pitrou:
Probably.

[asfimport]

Wes McKinney / @wesm:
@pitrou I'd prefer for "cast" to only deal with non-parametric type conversions (the data-loss / safe-unsafe flags don't count as conversion parameters per se)

Yes I agree with a review / normalization of function names before it's too late

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 7755
#7755