No file write/read api?

[andmm]

The directory api is fairly complete so I was surprised not to see the same with basic file handling. Any reasons for the absence?

[saprykin]

There was an idea to go for IO streams in general and then couple them with async loop. But sadly it was never implemented. But the project is open for contributions :)

[andmm]

Wouldn't be in the spirit of the library to use the platform native calls instead of abstracting it away? Like the posix API, win32 CreateFile, etc.

This seems like a fun little project and I can look into it but would it have to support all those platforms listed on the main page? I can get away with win32 and POSIX but I know very little about the other ones like amigaOS and so on.

[saprykin]

I would see two layers: native calls for files/sockets/etc, and then a layer of IO streams on top. So yes, file layer with native support is needed anyway.

I would say majority of OS list is covered by Unix and Windows, the rest of the exotic zoo either has Unix layer or a few would be used. I still do have access to most of them and can test/correct. The key is to have a good test coverage, then fixing exotics is relatively easy.

[andmm]

Alright, I'll get started on it. I'll do the basic native layer first for win32 and unix and I'll post a draft here so you can take a look if it fits with the library style properly. (is there a style guide page?).

I'll take a look at async for those platforms once I'm done with that. Then we can think about that I/O stream async abstraction that I'd assume you're thinking something along the lines of node (libuv).

I have another issue I wanna discuss but I'll open a new one so we can keep the discussion relevant here :)

[saprykin]

Unfortunately there is no style guiding doc, although I think it’s in open issues. I suggest you to take a look on socket or threading module to get an idea of naming conventions, docs and API. Then scope the API you want to implement before writing the code. It would also help to understand how it can fit with sockets under IO streams.

And feel free to reach out in case of any questions or troubles.