Hey! Really loving the direction of this library so far. I see in Platform.h that web/emscripten/wasi support is "planned" and that there are a few references to it throughout the codebase. What does the timeline look like on web support? Is that the current focus? Or is that much farther out?

We should really add a GitHub pipeline that fails if the code is not formatted with clang-format.

The script should be along these lines:

SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )
ROOT_DIR="${SCRIPT_DIR}/.."
SOURCE_DIR="${ROOT_DIR}/../SC"
HOST_TOOLS="${ROOT_DIR}/_Build/HostTools"
CLANG_FORMAT="$HOST_TOOLS/clang/bin/clang-format"
cd "${SOURCE_DIR}" && find . \( -iname \*.h -o -iname \*.cpp -o -iname \*.mm -o -iname \*.m -o -iname \*.inl \) -not \( -path "*/Dependencies/*" -o -path "*/Build/Windows/resource.h"  \) | xargs "${CLANG_FORMAT}" -i

Hello, unfortunately I have an issue with SCLib on windows. I got an exception in the Async module.

Details of my environment:

• VS2022 V17.9.6
• Win10 22H2
• Intel Core i3 with 12Gb RAM
• (I also tested the build on another machine (Core i5) with similar results.)

Details of the error:
"Exception thrown at 0x00007FF7DDFD1536 in SCTest.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF."

Call Stack:
SCTest.exe!SC::detail::AsyncWinOverlapped::getUserDataFromOverlappedSC::AsyncRequest(_OVERLAPPED * lpOverlapped) Line 32 C++
SCTest.exe!SC::AsyncEventLoop::KernelQueue::getAsyncRequest(unsigned int index) Line 200 C++
SCTest.exe!SC::AsyncEventLoop::Private::runStepExecuteCompletions(SC::AsyncEventLoop::KernelQueue & queue) Line 610 C++
SCTest.exe!SC::AsyncEventLoop::Private::runStep(SC::AsyncEventLoop::Private::SyncMode syncMode) Line 573 C++
SCTest.exe!SC::AsyncEventLoop::runNoWait() Line 269 C++
SCTest.exe!SC::AsyncEventLoop::Internal::createSharedWatchers(SC::AsyncEventLoop & eventLoop) Line 134 C++
SCTest.exe!SC::AsyncEventLoop::create(SC::AsyncEventLoop::Options options) Line 261 C++
SCTest.exe!SC::FileSystemWatcherTest::eventLoopSubdirectory(const SC::StringView appDirectory) Line 117 C++
SCTest.exe!SC::FileSystemWatcherTest::FileSystemWatcherTest(SC::TestReport & report) Line 23 C++
SCTest.exe!SC::runFileSystemWatcherTest(SC::TestReport & report) Line 334 C++
SCTest.exe!main(int argc, const char * * argv) Line 157 C++

Locals of the AsyncWinOverlapped::getUserDataFromOverlapped function:
offsetOfOverlapped -> 8
offsetOfAsync -> 0

I hope, it will be enough info to find the problem.

Hi there, cool project!

Any plans to support io_uring backends for Async I/O (and event loop)?

Currently VSCode build and run configuration exist only for macOS and Linux.
It would be cool to have a VSCode build / run configuration for Windows.

Ideally it should be possible building using the generated Visual Studio file or the Makefile, that would need to be modified, as it's currently Posix only.

Currently SC::Atomic<T> only supports bool and int32_t.

Support for more types should be added and also we need some way of adding real tests or at least validations that the various compiler specific directives are doing the right thing.

We definitively can use SC::ThreadPool to run Async File Read / Write on background threads for all backends that don't have native support for it (i.e. anything excluding io_uring for buffered disk files).

We should really create some GitHub pipelines that are:

• Bootstrapping the build (Calling SCBuild.bat(windows), SCBuild.sh(Linux / macOS)
• Building the unit test (SCTest project or makefile)
• Running the test suite (SCTest executable)

And this should be running on:

• macOS
• Windows
• Linux

so that we can make it a prerequisite for any MR

Useful algorithms could be:

• Unique
• Better Sort (Insertion ?)
• Min / Max
• Min / Max Element
• Rotate
• Count / Count If

Sockets library only supports TCP so far and adding UDP support would be great 😀

I'm getting the following compilation failure. Looks like the functions in LibC.h are missing noexcept(true).

This is on gcc 13.2.1 on Fedora.

In file included from /home/nimble/dev/example/thirdparty/sc/Libraries/FileSystem/Internal/FileSystemPosix.inl:11,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/FileSystem/FileSystem.cpp:12,
                 from /home/nimble/dev/example/thirdparty/sc/SC.cpp:9:
/usr/include/string.h:43:14: error: declaration of ‘void* memcpy(void*, const void*, size_t) noexcept’ has a different exception specifier
   43 | extern void *memcpy (void *__restrict __dest, const void *__restrict __src,
      |              ^~~~~~
In file included from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/../../File/../Strings/../Strings/../Foundation/Assert.h:6,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/../../File/../Strings/../Strings/StringIterator.h:4,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/../../File/../Strings/StringView.h:4,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/../../File/FileDescriptor.h:7,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/../Async.h:12,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/AsyncPrivate.h:2,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/AsyncLinux.inl:3,
                 from /home/nimble/dev/example/thirdparty/sc/Libraries/Async/Async.cpp:10,
                 from /home/nimble/dev/example/thirdparty/sc/SC.cpp:6:
/home/nimble/dev/example/thirdparty/sc/Libraries/Async/Internal/../../File/../Strings/../Strings/../Foundation/../Foundation/LibC.h:16:11: note: from previous declaration ‘void* memcpy(void*, const void*, SC::size_t)’
   16 |     void* memcpy(void* dst, const void* src, SC::size_t n);
      |           ^~~~~~

Hello, great project you've got going on here.
Are there any plans or intentions to make the libraries easy to install with any popular package managers? Like vcpkg?
Installation could be as easy as vcpkg install sane-cpp-libraries, and would ease adoption.

Hello. Is it possible add a database access module abstraction. Similar to JDBC or golang database/sql?

We should compute code coverage for all three supported platform.

It would be cook to display a code coverage badge somewhere in the readme.

Threading library really needs to be complete, with the addition of a semaphore and a scoped mutex lock / unlock class.