dstep VS RIIR

You might also be interested in dstep, a tool that can generate D bindings from C header files.

- C, Objective-C = https://github.com/jacob-carlborg/dstep

> its test blocks make unit testing trivial to integrate.

Again, D also has this:

https://tour.dlang.org/tour/en/gems/unittesting

  void main() {

It's a C lib, generating bindings is super easy https://github.com/jacob-carlborg/dstep

There is no need to maintain bindings that can be automatically generated, wich can easily get outdated if the C project is actively developped

Anyways, someone went a ahead and updated it: https://github.com/Soaku/raylib-d

Not quite as seamless as Zig, but dstep is an external program that leverages libclang to do the same thing (and generates a D module for you), as well as e.g., smartly convert #define macros to inlineable templates functions :)

https://github.com/jacob-carlborg/dstep

It was, imo, inflated by the comments pointing to the RiiR sentiments, not the comments to that effect itself. Even repositories 'collecting' such instances (e.g. https://github.com/ansuz/RIIR) are largely not collections of making anyone to change their own software but just projects that happen to be written in Rust. (these out-of-scope issues are not being tagged appropriately). Overhyped controversy by all sides.

Dunno what news you have missed but there's entire internet brigades dedicated sorely to spam projects with "rewrite it in rust". There's even a repo documenting this.

The OP post in the link references https://transitiontech.ca/random/RIIR (Rewrite it in Rust) as a meme.

Yes, one can hope, but I wouldn't bet on it and I wouldn't suggest to RIIR. I don't want to be that person that pops up uncalled for and asks to Rewrite It In Rust. One might think "Oh it is just one additional issue to the ~2.2k already opened mypy issues" if they have at all realized that there are that many open issues.

It's died down a bit now, but there is/was a non-trivial amount of stupidity from Rust advocates whenever someone ran into a memory problem with C/C++ to "re-write it in rust" or to just rewrite things in general. (IE https://transitiontech.ca/random/RIIR)

Or even better, RIIR the Windows kernel!

What is it with people asking for rust rewrites of Xorg this week? https://github.com/ansuz/RIIR/issues/83

The second language is Rust, and I went with that partly because rewriting C in Rust is a meme in itself, and in part because it was much easier to think of how to nicely fix that bug in Rust than it was in C (just add a = to the range to be end-inclusive).