diff options
| -rw-r--r-- | .ci.cmake | 3 | ||||
| -rw-r--r-- | Doxyfile | 2 | ||||
| -rw-r--r-- | release_notes.md | 7 |
3 files changed, 8 insertions, 4 deletions
@@ -21,6 +21,9 @@ if(NOT CTEST_DISABLE_TESTING) if(WIN32) # Appveyor's Windows version doesn't permit unprivileged creation of symbolic links ctest_test(RETURN_VALUE retval EXCLUDE "shared_fs_mutex|symlink") + else("$ENV{CXX}" MATCHES "clang") + # clang 10 with libc++ in C++ 20 currently segfaults + ctest_test(RETURN_VALUE retval EXCLUDE "shared_fs_mutex|llfio_hl--coroutines") else() ctest_test(RETURN_VALUE retval EXCLUDE "shared_fs_mutex") endif() @@ -38,7 +38,7 @@ PROJECT_NAME = "LLFIO" # could be handy for archiving the generated documentation or if some version # control system is used. -PROJECT_NUMBER = "v2.00 late alpha" +PROJECT_NUMBER = "v2.00 late beta" # Using the PROJECT_BRIEF tag one can provide an optional one line description # for a project that appears at the top of each page and should give viewer a diff --git a/release_notes.md b/release_notes.md index 73d0ee23..be23ab65 100644 --- a/release_notes.md +++ b/release_notes.md @@ -23,19 +23,20 @@ as Intel Optane. It is a complete rewrite after a Boost peer review in August 2015. Its github source code repository lives at https://github.com/ned14/llfio. -- `llfio::path_view` is expected to enter the C++ 23 standard. `llfio::file_handle` and `llfio::mapped_file_handle` are on track for entering the C++ 23 standard. +- LLFIO is the reference implementation for these C++ standardisation: + - `llfio::path_view` is expected to enter the C++ 23 standard. + - `llfio::file_handle` and `llfio::mapped_file_handle` are on track for entering the C++ 23 standard. - Portable to any conforming C++ 14 compiler with a working Filesystem TS in its STL. - Note that VS2019 16.3 and libc++ 11 dropped support for Filesystem in C++ 14, so for those LLFIO's cmake forces on C++ 17. - Fully clean with C++ 20. - Will make use of any Coroutines, Concepts, Span, Byte etc if you have them, otherwise swaps in C++ 14 compatible alternatives. - - NOTE that libstdc++ does not currently provide symbols for `<codecvt>` if you are building in C++ 20, so linking LLFIO programs on libstdc++ if in C++ 20 will fail. Either use a different STL, manually rebuild libstdc++, or use C++ 17. + - NOTE that Ubuntu 18.04's libstdc++ 9 does not currently provide symbols for `<codecvt>` if you are building in C++ 20, so linking LLFIO programs on libstdc++ on that Linux if in C++ 20 will fail. Either use a different STL, manually rebuild libstdc++, or use C++ 17. - Original error code is always preserved, even down to the original NT kernel error code if a NT kernel API was used. - Optional configuration based on [P1028](https://wg21.link/P1028) *SG14 status_code and standard error object for P0709 Zero-overhead deterministic exceptions*. - Race free filesystem design used throughout (i.e. no TOCTOU). - Zero malloc, zero exception throw and zero whole system memory copy design used throughout, even down to paths (which can hit 64Kb!). - Comprehensive support for virtual and mapped memory of both SCM/DAX and page cached storage, including large, huge and super pages. -- Works very well with the C++ standard library, and is being proposed for standardisation into C++. See <a href="https://wg21.link/P1031">P1031 *Low level file i/o*</a>. \note This code is of late beta quality. It has been shipping in production with multiple vendors for some years now. It is quite reliable on Windows and Linux (less well tested on Mac OS), so be careful when using it! |