Documentation

The IO operation to perform. The idea of splitting it out into a type like this is to enforce some kind of auditing.

Is this IO operation something that we allow in untrusted code, namely script input. This is not a completely firm security boundary, as even safe IO operations allow reading of arbitrary files, but the idea is to make it possible to benchmark untrusted Futhark programs (assuming you also use --safe, of course).

An IO intrinsic, which determines its operation from the type at which it is instantiated and its arguments, of which the first is always a file name. The file name is fetched in full before the intrinsic sees it, but any other argument is passed as-is, and so may contain references to values residing on a server.

Determine which IO operation this is.

If you want to add a new one, then remember to also add it as an intrinsic in the type checker, and probably also to the prelude.

Run an IO operation. Arrays are put on the server, if one is given.

Resolve relative file paths in the operation relative to the given directory, rather than the current working directory.