2 ms·
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
by pjmlp 1y ago
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.
- TobbenTM 1y agoThe Ladybird project started a similar journey, and indeed they are mainly waiting on Swift 6+ features as documented in their blockers issue: https://github.com/LadybirdBrowser/ladybird/issues/933 https://github.com/LadybirdBrowser/ladybird/issues/933
- jen20 1y agoI 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.
- pjmlp 1y agoWhich could be a good reasoning, assuming it is being enforced somehow, in regards to modern best practices, which is usually the main issue.
- jen20 1y agoIndeed - 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.