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
I guess that quasi-paths which start or end with slashes need vertical bars around them.
Vertical bars are now eliminated as an escaping mechanism, so this would not be an option.
But current thinking is that PATH! and TUPLE! do not come in quasiforms or antiforms. That simplifies this, so if you see:
~/foo/~
You know that's not a QUASI-PATH! because there are no QUASI-PATH!s.
A remaining problem is the special case of / being a WORD! (to make it assignable and customizable as a division operator). Then ~/~ would be an quasi-word. That may just be a consequence of the design, in which case we'd just have to disallow the creation of paths with ~ in the first and second slots.
Quasi-Voids were made legal in PATH! and TUPLE!, specifically to facilitate things like:
But this creates an ambiguity with things like:
... which could be a regular path with quasi-voids in the first and last positions... or a quasi-path with blanks in the first and last positions. 😦
I guess that quasi-paths which start or end with slashes need vertical bars around them.
Annoying, but, I think it's worth it.
~/projects/stuff
is legal in Redbol and I'd rather not lose the ability to do that.The text was updated successfully, but these errors were encountered: