How do I handle crate and package name mismatches in REPL?

[vi]

Example: prettytable-rs.

$ evcxr 
Welcome to evcxr. For help, type :help
>> extern crate prettytable;
error: no matching package named `prettytable` found
>> extern crate prettytable_rs;
error: no matching package named `prettytable_rs` found
>> :dep prettytable-rs = "*"
(waiting)
can't find crate for `prettytable_rs`
>> extern crate prettytable;
error: no matching package named `prettytable` found

[Celti]

The issue seems to be that add_extern_crate() in eval_context.rs automatically uses the normalized package name as the crate name. It's called by process_command() from command_context.rs — naively, the syntax for :dep could be extended to allow specifying separate package and crate names.

OTOH, extern crate goes away in the 2018 edition, and I have no idea how this might interact with that.

[vi]

As I simple workaround, :dep prettytable-rs = "*" may still fail with can't find crate for prettytable_rs, yet add the dependency, allowing further explicit extern crate prettytable; to succeed (maybe also after first failing to find a package).

[davidlattimore]

Thanks for the report, I hadn't realised that crates could use a different name for the library. This looks like a duplicate of #15, so lets continue discussion there...