Skip to content
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

syn 0.15.22 breaks diesel_derives #1921

Closed
2 tasks done
trha opened this issue Nov 26, 2018 · 4 comments
Closed
2 tasks done

syn 0.15.22 breaks diesel_derives #1921

trha opened this issue Nov 26, 2018 · 4 comments

Comments

@trha
Copy link
Contributor

trha commented Nov 26, 2018

Setup

Versions

  • Rust: 1.30.1
  • Diesel: 1.33
  • Database: PostgreSQL
  • Operating System macOS 10.14.1

Feature Flags

  • diesel: default

Problem Description

The latest version of the syn crate exports a new Result type alias, which collides with std::result::Result and makes diesel_derives fail to compile.

What are you trying to accomplish?

Use diesel_derives.

What is the expected output?

diesel_derives compiles successfully.

What is the actual output?

error[E0107]: wrong number of type arguments: expected 1, found 2
  --> diesel_derives/src/util.rs:48:84
   |
48 | pub fn ty_for_foreign_derive(item: &DeriveInput, flags: &MetaItem) -> Result<Type, Diagnostic> {

Are you seeing any additional errors?

No

Steps to reproduce

Compile diesel_derives from master.

Checklist

  • I have already looked over the issue tracker for similar issues.
  • This issue can be reproduced on Rust's stable channel. (Your issue will be
    closed if this is not the case)
@weiznich
Copy link
Member

cc @dtolnay because potential breaking change in syn.

@dtolnay
Copy link

dtolnay commented Nov 26, 2018

Thanks for the ping. This is why you should only glob import from modules that are documented for glob importing, like preludes. Neither the standard library nor I am going to consider something like this a breaking change for affecting glob imports.

@weiznich
Copy link
Member

@dtolnay See this comment on the corresponding PR. I do not consider that as major breaking change that requires some action from your side. The ping was to just let you know that this issue exists 😉

icefoxen added a commit to icefoxen/diesel that referenced this issue Dec 6, 2018
@weiznich
Copy link
Member

weiznich commented Jan 4, 2019

Fixed on master

@weiznich weiznich closed this as completed Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants