strop VS cargo-mutants

I am completely rewriting strop, (the code sucks, and I know Rust a lot better than when I started, so I wanted to make it a bit better structured and more idiomatic). And I like to have static analysis make sure my code has certain qualities, so I stick this:

Do you think it's an architecture for strop then? It has a focus on code-generation on platforms not well supported by mainstream compilers

Here is a project for generating code for CPUs that do not have much support from mainstream compilers. Currently supported are the 6502 and the STM8 (I'll possibly be adding others in the future, feature requests welcome).

I could use some help on my project strop. Feel free to take a look and see if it's the kind of thing you feel you could contribute to! but be aware that the quality of the codebase is poor. There's a pull request to address this though.

It is my first time of making a Rust library. Actually, my project strop has been a binary crate and only recently have I started trying to use it from a different crate. This is happening on the breakapart branch.

Still working on a big rewrite of strop.

Hadn't thought of this. I even encountered it recently too.

I am still working on strop. (TL;DR alternative to compiled code, it's evolved code. Tell it which function you want and which registers to use, and it'll randomly generate an assembly language program that does what you wanted)

Finally getting round to parallelizing strop.

I have a similar story. I developed strop in Rust after doing a similar thing in C. And even though I knew no Rust when I started, and even though it's the hardest problem I've done on my own, it's like the language and everything set me up for success.

Hi, distcc's original author here. It's really nice that people are still enjoying and using it 20 years later.

I have a new project that is in a somewhat similar space of wrapping compilers: https://github.com/sourcefrog/cargo-mutants, a mutation testing tool for Rust.

Hi Rusty!

For a later hack in the same vein, check out https://github.com/sourcefrog/cargo-mutants

cargo-mutants got a couple of releases over the weekend, fixing some environment-triggered bugs on Windows and Linux ecryptfs, and adding a better overall progress indicator (demo: https://asciinema.org/a/481375). It is getting better at avoiding uninteresting or pointless mutations, although there's a lot more to do there, and at printing function name paths well.

While working on Conserve and cargo-mutants I felt that existing Rust progress-bar libraries like Indicatif didn't give me enough control of how the bar was drawn, or at least I was working around them to insert my own text. For example, I wanted to draw several counters into a single line, and it seems like the only way to do that is to just push in a text string.

Continuing with some fast-follow enhancements in cargo-mutants in response to user feedback: for example doctests are typically slow and in some trees not important for coverage, so you can now skip them.

I got cargo-mutants to a state where I felt I could announce it and ask for public feedback.