wasi-filesystem icon indicating copy to clipboard operation
wasi-filesystem copied to clipboard

Filesystem API for WASI

Results 31 wasi-filesystem issues
Sort by recently updated
recently updated
newest added

and in the imports.md as those comments are duplicated there.

The `filesize` type is defined as unsigned `u64`. In POSIX, `off_t` is a signed type. Most practical implementations won't support file sizes >= 263, so: what error code should implementations...

Given WASI's CloudABI heritage I understand why preopens currently are the way that they are. But they feel like something that should be just an host implementation detail. Ie. could...

This was originally brought up by @dbaeumer - having to have a function call per directory entry to read through the directory entry stream might introduce unnecessary performance costs for...

These flags are all about providing data integrity guarantees, however to my knowledge, no one has yet investigated the degree to which these guarantees could be made in a portable...

I've been thinking about how trash management might translate to WASI and wanted to layout a few sticking points that I can see WASI potentially running into. ### Rational For...

Preopening file descriptors works well for directories with configuration/data because those directories are known for a given program. It also works fine for short-lived CLI programs because the directories they...

It would be nice if the filesystem API were allowed to support file-dir duality, tho we wouldn't expect most implementations to support it. Many filesystems, from Mac "System 7" to...

Many applications today (or at least many CLI apps) rely on the idea of a "current directory" of the calling process (e.g. `getcwd` and `chdir`). Currently, though, WASI doesn't define...

I'm trying to figure out what signatures the current source build as, and there are some dependencies to get this to build which are also in flux. One thing that...