I'm writing a Path type in my programming language but not sure what methods belong on a Path.
Should I have some_path.read_string() or fs::read_string(some_path) instead?
I love .method() for IDE completion, but I don't want Path to be cluttered. I'm also trying to avoid UFCS.
Futhark's design is deliberately trying to stay simple to keep long term design sustainable.
The author also has an interesting discussion of relative versus absolute paths in import syntax, and how relative paths can make local analysis easier.
It is *really* hard to find a good screenshot for a CLI tool when users are on a mobile browser.
This is the best I've come up with so far. I'm showing the terminal GUI to show where you'd use the tool.
I'm also trying several standalone screenshots to make it more comprehensible.