You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the POSIX API (pread/pwrite) for unbuffered I/O, many C++ projects utilize std::fstream for loading file content. Although std::fstream is intended for buffered I/O, I believe there are numerous use cases where kvikio could be seamlessly integrated into C++ projects by replacing std::fstream with kvikio's corresponding class.
Think this is a good writeup on how we might make KvikIO usage more idiomatic for C++ users
@jrhemstad as someone who has thought a lot about how to improve C++ users' CUDA experience, would be interested to hear your thoughts on what API would be best for us to present for file operations
This feature request aligns with Python's counterparts and is being mentioned here for reference:
seek
andtell
to PythonCuFile
object #576CuFile
object fromio.RawIOBase
#577In addition to the POSIX API (
pread
/pwrite
) for unbuffered I/O, many C++ projects utilizestd::fstream
for loading file content. Althoughstd::fstream
is intended for buffered I/O, I believe there are numerous use cases wherekvikio
could be seamlessly integrated into C++ projects by replacingstd::fstream
withkvikio
's corresponding class.Reference:
We could also explore the possibility of subclassing the following classes:
cc: @jakirkham
The text was updated successfully, but these errors were encountered: