miniblog.

I'm trying to teach LLMs to yak shave responsibly. It's normal to be programming and notice other clean ups that really ought to be done. I don't want it done in that PR though. Currently experimenting with asking the AI to just create hand-off tasks in the issue tracker.

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.