This is just a modification to the normal string type.
Currently you can define a string (not string function) with either " or ' and it will be checked against the allowed strings. With the addition of custom strings, I didn't want to remove that all together, but build on top.
So I added a custom string definition across the transpiler and parser to allow for it to be picked up as a valid token.
To skip the normal string check process and define a custom string you just have to add ~ before the string.
The following are valid strings.
~"This is a custom string"
~'This is another custom string'
However, the same strings without the ~ would register as invalid.
This is just a modification to the normal string type.
Currently you can define a string (not string function) with either
"or'and it will be checked against the allowed strings. With the addition of custom strings, I didn't want to remove that all together, but build on top.So I added a custom string definition across the transpiler and parser to allow for it to be picked up as a valid token.
To skip the normal string check process and define a custom string you just have to add
~before the string.The following are valid strings.
However, the same strings without the
~would register as invalid.