ceteia

But then, to use D for performance, would I then have to master both D, C and their interaction? That doesn't seem great. It's like having to learn 2 languages and also how they interact.

Does Rust really require reference counting? I thought Rust programs only used reference counting when types like Rc and Arc are used.

Swift seems to require reference counting significantly more than Rust.

I don't think that would be a silver bullet nor without drawbacks. It can be a rather bitter footgun when the same code can have different semantics in different editions or epochs. Automatic or semi-automatic conversion, as Rust has, helps it a bit, but not fully.

I think there are some smaller Rust ecosystems where they try to have some kind of ABI stability or dynamic linking. For instance, Bevy has some support for dynamic linking.

Edit:

Redox OS might be a better example, though its dynamic linking is for its Rust implementation of the C standard library.

https://www.redox-os.org/news/release-0.9.0/

> Relibc is also now key to our “stable ABI” strategy. The plan is for files to dynamically link against Relibc, which will provide a stable ABI for the dynamic linker. New POSIX functions will be added to Relibc, but none will be removed. That will leave us free to change the implementation of the services as Redox evolves, but still be able to run binaries compiled for older Redox versions.

Sorry to bother you, but I couldn't find any news on this, only a comment you made back in 2018 on GitHub; do you know if the HTTP APIs in Zig's standard library are here to stay, or if some of them might be removed? Another commenter wrote that the HTTP client is used for Zig's package management, but there is also the HTTP server.

Edit: Andrew confirmed that the HTTP client and server will stay in the standard library.

Regarding HTTP in Zig, it might be removed in 1.0, if I am reading this correctly. Though Zig std does have both an HTTP client and an HTTP server.

https://github.com/ziglang/zig/issues/910#issuecomment-39548...

Edit: Andrew confirmed that the HTTP client and server will stay in the standard library.

Regarding HTTP in Zig std library, might some of the API not be removed in the future?

https://github.com/ziglang/zig/issues/910#issuecomment-39548...

Might it have something to do with compiler heuristics? Compilers cannot analyze everything, since the more compilation time is spent on analysis, the slower compilation will be. So compilers might use heuristics to guess when to do analysis and how much, and when not to. As part of trade-offs between better optimization of compiled programs and decreasing compilation times.