https://registry.bazel.build/docs/rules_d

• Bitcode Compilation with LTO: Compile D libraries to LLVM bitcode for link-time optimization. See docs/bitcode_compilation.md for details.
• Flexible Toolchain Configuration: Support for different D compilers (DMD, LDC, GDC)
• Dependency Management: Seamless integration with C/C++ libraries
• Interface Files: Support for D header/interface files (.di)
• Version Identifiers: Conditional compilation with version identifiers

From the release you wish to use: https://github.com/bazel-contrib/rules_d/releases copy the WORKSPACE snippet into your WORKSPACE file.

To use a commit rather than a release, you can point at any SHA of the repo.

For example to use commit abc123:

1. Replace url = "https://github.com/bazel-contrib/rules_d/releases/download/v0.1.0/rules_d-v0.1.0.tar.gz" with a GitHub-provided source archive like url = "https://github.com/bazel-contrib/rules_d/archive/abc123.tar.gz"
2. Replace strip_prefix = "rules_d-0.1.0" with strip_prefix = "rules_d-abc123"
3. Update the sha256. The easiest way to do this is to comment out the line, then Bazel will print a message with the correct value. Note that GitHub source archives don't have a strong guarantee on the sha256 stability, see https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes/