BodkinsOdds

3 ms·

1. 1.▲
   by BodkinsOdds 2y ago

   C++ is already so reliant on optimizing `const&` parameters that I can't imagine why you wouldn't use them if you happen to be stuck with a shitty embedded toolchain (or MSVC) that can't be relied on to pass struct parame
2. 2.▲
   by BodkinsOdds 2y ago

   Needing that MakeArguments macro makes this substantially worse than just defining an aggregate struct for your arguments and using designated initializers. I've never wanted to reorder named arguments anyway, I've only ever wante
3. 3.▲
   by BodkinsOdds 2y ago

   There's a couple: https://github.com/stackotter/swift-cross-ui (Linux + Windows) https://github.com/TokamakUI/Tokamak (WASM + MacOS + some Ubuntu support) They both had to rewrite the entire
4. 4.▲
   by BodkinsOdds 2y ago

   - Anonymous enums/structs in parameters/match statements I'm not sure what you mean by this, could you elaborate?
5. 5.▲
   by BodkinsOdds 2y ago

   Nope. For the foreseeable future, stable ABI on other platforms is basically only going to happen if a distro starts supporting an ABI stable standard library on their own.
6. 6.▲
   by BodkinsOdds 2y ago

   Go is the only one of the three that directly uses syscalls. Rust and Swift both go through libc. Swift never even had the option of directly using syscalls, since it was originally designed for MacOS, and syscalls are so unstable there tha