New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the trait bound `<expression::count::CountStar as expression::Expression>::SqlType: sql_types::ops::Add` is not satisfied #1731

Closed
llxxbb opened this Issue May 25, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@llxxbb

llxxbb commented May 25, 2018

  • Rust: 1.28-nightly
  • Diesel: 1.3.0
  • Database: sqlite
  • Operating System win 10

diesel = { version = "1.3", default-features = false, features = ["sqlite","chrono"] }

error[E0277]: the trait bound <expression::count::CountStar as expression::Expression>::SqlType: sql_types::ops::Add is not satisfied
--> C:\Users\llxxb.cargo\registry\src\github.com-1ecc6299db9ec823\diesel-1.3.0\src\expression\count.rs:58:39
|
58 | #[derive(Debug, Clone, Copy, QueryId, DieselNumericOps)]
| ^^^^^^^^^^^^^^^^ the trait sql_types::ops::Add is not implemented for <expression::count::CountStar as expression::Expression>::SqlType
|
= help: consider adding a where <expression::count::CountStar as expression::Expression>::SqlType: sql_types::ops::Add bound
= help: see issue #48214
= help: add #![feature(trivial_bounds)] to the crate attributes to enable

@weiznich

This comment has been minimized.

Contributor

weiznich commented May 25, 2018

@BartMassey

This comment has been minimized.

BartMassey commented Jun 8, 2018

Looks like a change to rustc was pushed about 4 hours ago that is reported to resolve this issue. This would be a good time to close it, if it hadn't been closed 14 days ago. :-) rust-lang/rust/pull/#51042

@Eijebong

This comment has been minimized.

Member

Eijebong commented Jun 8, 2018

It's not merged yet ;)

@BartMassey

This comment has been minimized.

BartMassey commented Jun 8, 2018

Indeed. So maybe we should wait to have closed the issue a little longer. :-)

@Eijebong

This comment has been minimized.

Member

Eijebong commented Jun 8, 2018

No because it's not something that's actionable on our part so it shouldn't even have been opened here in the first place ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment