Quasi-Void Rendering Ambiguity in Paths

Quasi-Voids were made legal in PATH! and TUPLE!, specifically to facilitate things like:

dir: first [~/projects/stuff]

But this creates an ambiguity with things like:

~/foo/~

... 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.

~|/foo/|~  vs.   ~/foo/~
~|/foo|~   vs.   ~/foo
~|foo/|~   vs.   foo/~

~foo~ and ~foo/bar~ is unambiguous

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.

Provide feedback