rustyline VS Clippy

This latest release adds a Rustyline-based REPL and additional tools for using the filesystem as a relational database. The new init subcommand lets you declare the primary key by which a directory (and its subdirectories) are indexed, while ins and del now allow insertion and deletion of records while keeping related indices up to date. ls is helpful in the REPL, showing Ghee's view of the world.

That what gnu readline is good at, interpreter like interface. There is also this one https://github.com/kkawakam/rustyline

In the process of implementing Marwood's web REPL, I ported rust's [Rustyline](https://github.com/kkawakam/rustyline) readline library to an Xterm.js typescript addon called [xterm-readline](https://github.com/strtok/xterm-readline/).

There is rustyline, which is a readline implementation. It supports line editing in emacs or vi mode (selectable). I don't know if it can operate on two strings as input, but if your program takes input from a terminal, this could be what you are looking for.

Not sure if it will help in this case (docs always take effort to write and make good), but most crates have an examples directory in the root of their repo which can be helpful in the absence of guide-level docs https://github.com/kkawakam/rustyline/tree/master/examples

https://crates.io/crates/rustyline - readline clone in Rust

https://github.com/kkawakam/rustyline (literally, input a command)

Also based on popular demand, the REPL tool now uses a slightly enhanced version of rustyline for line editing and history.

it is also worth checking if library contains examples. this one does.

Maybe try reedline or rustyline and see if they meet your needs?

I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block

there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689

You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .

I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)

Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.

clippy is a great place to get started :) though it isn't exactly new.

clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.

Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.

Check out the readme for more information.

They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.