On: Rewriting Rust

[lostmsu]

Regex one stands out as a negative example here. Why does it have to be built-in instead of exposing a str -> bool filter lambda?

[sethaurus → lostmsu]

How does one pass a lambda to a CLI tool? Outside of using a regex or equivalent pattern syntax, I'm struggling to understand what you are proposing here.

[lostmsu → sethaurus]

This is in a context of file watching library. Although I'm not sure cargo-watch supports or even needs to support regex.

[mirashii → lostmsu]

Now you need a general purpose embedded language interpreter to express your filter lambda? I'm not sure you've really made anything simpler.

[rowanG077 → mirashii]

I don't see why you want an embedded interpreter for this. Can you explain?

[tempodox → rowanG077]

If you give a lambda to cargo-watch instead of a regexp, it has to be evaluated. Hence interpreter.

[rowanG077 → tempodox]

Why would you evaluate it using an interpreter? Since you are using it in the context of a rust lambda you compile it. You just have a rust file that calls cargo-watch as a library. Crafting an interpreter seems like an incredibly bad idea.

[mirashii → rowanG077]

But now you have to know at compile time what you're watching, which is not what cargo-watch or any of the similar commands like entr do.

[rowanG077 → mirashii]

Considering you have a rust file and the dependency why wouldn't you compile it? It's not like rustc is not available when you are using cargo-watch.

[tempodox → rowanG077]

Anyway, doing all that just so you don't have to write a regexp has all the hallmarks of overkill. Keep it simple.