- 23 Dec, 2017 1 commit
-
-
Kenton Varda authored
The disk-backed implementations were already inherently threadsafe. Making this explicit allows callers to rely on it. This is particularly useful for SchemaParser, which is intended to be threadsafe.
-
- 21 Dec, 2017 1 commit
-
-
Kenton Varda authored
-
- 11 Dec, 2017 1 commit
-
-
Kenton Varda authored
There are two purposes: 1. Convert all the way to/from wchar_t, to make interfacing with Win32 filesystem APIs easier. 2. Use and handle '\\?\'-style paths. This prefix apparently opts into support for longer filenames. This seems like a good idea for any new programs! (It also opts out of support for using forward slashes as path separators and handling of '..', but kj::Path already handles these, so great.)
-
- 27 Apr, 2017 1 commit
-
-
Kenton Varda authored
This has three main parts: * The Path data structure, a more-explicit approach to file paths. * The File/Directory abstract interfaces. * The "InMemory" implementations of File and Directory. Disk-based implementations will come in a future commit.
-