BodkinsOdds
Re:Fun with C++26 reflection: Keyword Arguments
on Tuesday February 11, 2025 @01:47AM (#43009745)
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 parameters efficiently.
Re:Fun with C++26 reflection: Keyword Arguments
on Tuesday February 11, 2025 @01:44AM (#43009727)
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 wanted to elide some of them.
Re:Swift Static Linux SDK
on Sunday June 23, 2024 @08:07AM (#40766825)
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 backend from scratch, because SwiftUI is very, very closed source. But Tokamak does have an import that just forwards to SwiftUI on Apple platforms.
Re:Swift Static Linux SDK
on Saturday June 15, 2024 @01:47PM (#40691334)
- Anonymous enums/structs in parameters/match statements
I'm not sure what you mean by this, could you elaborate?
Re:Swift Static Linux SDK
on Saturday June 15, 2024 @01:38PM (#40691245)
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.
Re:Swift Static Linux SDK
on Saturday June 15, 2024 @01:34PM (#40691208)
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 that they've changed in minor version updates.