Suppressing static lifetimes from Text (and other modules ?)

Is your feature request related to a problem? Please describe. While working with Inquire to setup a name verification, I look through an HashMap that is contained by a struct and pass that struct through a ref, that looks like this :

struct Container {
   ids: HashMap<String, usize>,
}

fn type_id(container: &Container) -> InquireResult<String> {
   Text::new("type the id:")
       .with_validator(|text:&str| {
           // Validation process...
           if container.ids.contains(text) {
               Validation::Invalid("nope, exists".into())
           } else {
              Validation::Valid
           }
      }).prompt()
}

But I can't pass a simple ref to the validator as it needs a static lifetime, and I rather avoid cloning the hashmap / container (they can get pretty big) or sharing them through an Rc<RefCell<T>>.

Describe the solution you'd like I tried to implement a solution which is available on my fork : https://github.com/stormshield-hf/inquire/commit/2a07dc44a84534f2023a2a41c40cf8ca5afd0fcd (branch in case I end up doing other changes : https://github.com/stormshield-hf/inquire/tree/work/hf/remove_static_lifetimes)

TLDR: We add a second lifetime to the Text struct which is associated to validators (and the autocompleter) and add a clone implementation that specializes on 'b: static.

The advantage of this solution is that it will keep the existing clone impl. The main disadvantage is that it will be a breaking change as we need to add a lifetime.

Describe alternatives you've considered Another solution we tried is specifying that validator must be 'a rather than 'static but we must specialize the Clone as 'a: static, which might be an even greater breaking change depending on the usage of the lib.

Additional context Add any other context or screenshots about the feature request here.

mikaelmello / inquire

Suppressing static lifetimes from Text (and other modules ?) #241