4 ms·

Walter Bright has said on several occasions that compilation speed was one of his design goals for D.

by gHosts 7y ago

unlinked_dll 7y ago
Recently on the "On the Metal" podcast (which is fantastic) Johnathon Blow had a mini rant on compilation speeds and mentioned that the Jai compiler is incredibly fast.
- atombender 7y ago
  Jai apparently — I think it's mentioned in that podcast — has a dedicated backend for debug builds that's optimized for fast code generation and doesn't use LLVM. Sounds like what Cranelift is trying to do for Rust.
  - unlinked_dll 7y ago
    This seems to be the move for languages moving forward.
    - pjmlp 7y ago
      That is already the approach in Lisp, Scheme, Java, .NET, mainframe language environments, OCaml, Haskell, Eiffel, Dart, D and plenty others. By having a mix of interpreters, repls, JIT and AOT compilers, one can mix and match, using the fastest ones for development and the slow ones for the final release build.
zaphar 7y ago
If I'm reaching for Rust it's more than likely because I want it's borrow checker and pattern matching on enumerated types. To my knowledge D has neither of those so it's not really in the running here.
- earenndil 7y ago
  A borrow checker is currently in development for d, and pattern matching has been pseudo-implemented with metaprogramming.
- gmfawcett 7y ago
  "In the running" for what? Your personal list of preferences? There's no need to gate-keep this discussion because you favour pattern matching and borrow checking.
  - ajross 7y ago
    It was a personal statement, that's not gatekeeping. A more detached way to make the same point was that D didn't succeed (in the sense of market share) because it didn't reach "far enough" beyond what could already be done with C and C++. It brought real features to the table, but not "killer" ones. Rust did, which is why it's everyone's favorite new toy and why it's been largely (but not entirely, c.f. the linked article) forgiven for flaws like slow build times.

Walter Bright has said on several occasions that compilation speed was one of his design goals for D.

by gHosts 7y ago

Walter Bright has said on several occasions that compilation speed was one of his design goals for D.

Recently on the "On the Metal" podcast (which is fantastic) Johnathon Blow had a mini rant on compilation speeds and mentioned that the Jai compiler is incredibly fast.

atombender 7y ago
Jai apparently — I think it's mentioned in that podcast — has a dedicated backend for debug builds that's optimized for fast code generation and doesn't use LLVM. Sounds like what Cranelift is trying to do for Rust.
- unlinked_dll 7y ago
  This seems to be the move for languages moving forward.
  - pjmlp 7y ago
    That is already the approach in Lisp, Scheme, Java, .NET, mainframe language environments, OCaml, Haskell, Eiffel, Dart, D and plenty others. By having a mix of interpreters, repls, JIT and AOT compilers, one can mix and match, using the fastest ones for development and the slow ones for the final release build.

zaphar 7y ago

If I'm reaching for Rust it's more than likely because I want it's borrow checker and pattern matching on enumerated types. To my knowledge D has neither of those so it's not really in the running here.

earenndil 7y ago
A borrow checker is currently in development for d, and pattern matching has been pseudo-implemented with metaprogramming.
gmfawcett 7y ago
"In the running" for what? Your personal list of preferences? There's no need to gate-keep this discussion because you favour pattern matching and borrow checking.
- ajross 7y ago
  It was a personal statement, that's not gatekeeping. A more detached way to make the same point was that D didn't succeed (in the sense of market share) because it didn't reach "far enough" beyond what could already be done with C and C++. It brought real features to the table, but not "killer" ones. Rust did, which is why it's everyone's favorite new toy and why it's been largely (but not entirely, c.f. the linked article) forgiven for flaws like slow build times.