That was an experiment the team didn’t end up committing to - it’s been backed out. That said it was a fascinating dive into the flexibility of Swift, and the Konrad’s talk is excellent and worth watching.
Interesting, thanks for sharing, is there a rationale somewhere?
As someone that enjoys using C++ despite all its warts, I can imagine a few reasons, but would nonetheless an interesting read, in case that is public.
I guess that experience might also had an impact on ongoing Swift 6+ features.
I don’t know the specific reasons (and the pull request referenced in the merge commit appears to have been deleted), but my guess is that the extra complexity vs using modern C++ features was not worthwhile to the core FDB team.
Indeed - my guess is that there is a policy of "improve things as you touch that area of the codebase" rather than blanket rewriting of working code going on.
Huh, apparently so! It doesn't seem like much has happened since - there certainly aren't many pull requests which reference Swift [0] since it was restored.
"Swift as C++ Successor in FoundationDB" by Konrad Malawski (Strange Loop 2023)
https://www.youtube.com/watch?v=ZQc9-seU-5k