Alias `int-to-<ascii-or-utf8>` to `uint-to-<ascii-or-utf8>`

[hugoclrd]

The native functions int-to-ascii and int-to-utf8 take one argument that can be an int or uint. Which is rare in Clarity, that is usually picky with types.
Because of that, this function can look off at first glance:

(define-private (func (a uint))
  (int-to-ascii a)
)

A clarity developer might try to type uint-to.. but the auto-completion wouldn't be triggered, hence the suggestion add 2 aliases:

• uint-to-utf8
• uint-to-ascii

[LNow]

stacksgov/sips#95 (comment)

[hugoclrd]

Ah! Thanks for referencing it @LNow.
Looks like the conversation did not come to a conclusion at that time 🤔

[LNow]

The conclusion for me was simple - no clarity in Clarity 😬

[obycode]

Do you think the proposal for a generic to-string (or more likely to-ascii and to-utf8) in #82 would be more clear?

[brice-stacks]

We have to-ascii? as of Clarity 4.