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
Similar to how we have the Go math package exposed via TICKscript functions we should do the same for the strings package.
Some initial thoughts.
Only import functions that take strings args and other TICKscript primitives, not rune based functions.
Since the function names in the strings package are scoped by the strings. name in the Go language but TICKScript has global scope we need to decide on a consistent naming convention for these functions. Probably prefixing the functions with str will be enough.
The text was updated successfully, but these errors were encountered:
Similar to how we have the Go math package exposed via TICKscript functions we should do the same for the strings package.
Some initial thoughts.
strings.
name in the Go language but TICKScript has global scope we need to decide on a consistent naming convention for these functions. Probably prefixing the functions withstr
will be enough.The text was updated successfully, but these errors were encountered: