Skip to content
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.

Attempt to bound type parameter with a nonexistent trait StrAllocating #66

Closed
MattWindsor91 opened this issue Dec 23, 2014 · 4 comments
Closed

Comments

@MattWindsor91
Copy link

On Windows 64-bit, rust-lang/rust 62fb41c32, docopt b5e9e16 I get:

$ rustc --version
rustc 0.13.0-nightly (62fb41c32 2014-12-23 02:41:48 +0000)

$ cargo run -- -d'localhost:1351' -u'localhost:1350'
   Compiling docopt v0.6.18 (https://github.com/docopt/docopt.rs.git#b5e9e163)
warning: using multiple versions of crate `regex`
C:\MinGW\msys\1.0\home\mattbw\.cargo\git\checkouts\docopt.rs-643e15305361a76f\ma
ster\src\lib.rs:217:1: 217:24 note: used here
C:\MinGW\msys\1.0\home\mattbw\.cargo\git\checkouts\docopt.rs-643e15305361a76f\ma
ster\src\lib.rs:217 extern crate serialize;
                    ^~~~~~~~~~~~~~~~~~~~~~~
note: crate name: regex
C:\MinGW\msys\1.0\home\mattbw\.cargo\git\checkouts\docopt.rs-643e15305361a76f\ma
ster\src\lib.rs:216:1: 216:20 note: used here
C:\MinGW\msys\1.0\home\mattbw\.cargo\git\checkouts\docopt.rs-643e15305361a76f\ma
ster\src\lib.rs:216 extern crate regex;
                    ^~~~~~~~~~~~~~~~~~~
note: crate name: regex
C:\MinGW\msys\1.0\home\mattbw\.cargo\git\checkouts\docopt.rs-643e15305361a76f\ma
ster\src\lib.rs:486:41: 486:54 error: attempt to bound type parameter with a non
existent trait `StrAllocating`
C:\MinGW\msys\1.0\home\mattbw\.cargo\git\checkouts\docopt.rs-643e15305361a76f\ma
ster\src\lib.rs:486                where I: Iterator<S>, S: StrAllocating {
                                                            ^~~~~~~~~~~~~
error: aborting due to previous error
Could not compile `docopt`.

To learn more, run the command again with --verbose.

While the regex issues are #65, the StrAllocating error seems to be a new one, caused by this prq.

@marcusklaas
Copy link

Can confirm issue on Ubuntu 64bit.

@BurntSushi
Copy link
Member

Ah, yup. Looks like I'll have to switch to StrExt.

I'll fix this and the regex warnings in a few hours. :-)

@marcusklaas
Copy link

Cheers!

@BurntSushi
Copy link
Member

Fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants