Diesel does not build

[pie-flavor]

Setup

cargo build

Versions

• Rust: rustc 1.28.0-nightly (a1d4a9503 2018-05-20)
• Diesel: 1.2.2
• Database: MySQL
• Operating System Windows 10 1803

Feature Flags

• diesel: ["mysql", "r2d2", "chrono"]

Problem Description

Diesel does not compile.

What are you trying to accomplish?

Compile a program that depends on Diesel.

What is the expected output?

   Compiling diesel v1.2.2

What is the actual output?

   Compiling diesel v1.2.2
error[E0053]: method `metadata` has an incompatible type for trait
   --> C:\Users\Adam\.cargo\registry\src\github.com-1ecc6299db9ec823\diesel-1.2.2\src\mysql\types\mod.rs:88:25
    |
88  |     fn metadata(lookup: &()) -> MysqlType {
    |                         ^^^ expected associated type, found ()
    |
   ::: C:\Users\Adam\.cargo\registry\src\github.com-1ecc6299db9ec823\diesel-1.2.2\src\sql_types\mod.rs:402:25
    |
402 |     fn metadata(lookup: &Self::MetadataLookup) -> Self::TypeMetadata;
    |                         --------------------- type in trait
    |
    = note: expected type `fn(&<mysql::backend::Mysql as sql_types::TypeMetadata>::MetadataLookup) -> <mysql::backend::Mysql as sql_types::TypeMetadata>::TypeMetadata`
               found type `fn(&()) -> mysql::backend::MysqlType`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0053`.
error: Could not compile `diesel`.

Are you seeing any additional errors?

Nope.

Steps to reproduce

[dependencies.diesel]
version = "1.2.2"
default-features = false
features = ["mysql", "r2d2", "chrono"]

Checklist

• I have already looked over the issue tracker for similar issues.

[weiznich]

Duplicate of #1700

[charleschege]

I can't build any project that depends on diesel due to this bug. Any help?

[weiznich]

@iamcharleschege Look at the original issue for a workaround.(just use a older nightly from before 15/5/18) Otherwise there is nothing we could do beside waiting for rustc to fix that issue.
Please remember: Nightly is there for especially this case. To move forward without fear to break someone's code, because there is time before the change reaches the stable release.
This means you should test once a while against nightly but you shouldn't depend on nightly for code that needs to compile at any time. For this usecase there is the stable release.