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:
The native functions
int-to-ascii
andint-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: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