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

Compatibility with use_extern_macros #1933

Closed
2 tasks done
jimmycuadra opened this issue Dec 8, 2018 · 3 comments
Closed
2 tasks done

Compatibility with use_extern_macros #1933

jimmycuadra opened this issue Dec 8, 2018 · 3 comments

Comments

@jimmycuadra
Copy link
Contributor

jimmycuadra commented Dec 8, 2018

Versions

  • Rust: rustc 1.32.0-nightly (14997d56a 2018-12-05) (but this issue is applicable on stable)
  • Diesel: 1.3.3
  • Database: N/A
  • Operating System: macOS 10.14.1

Feature Flags

  • ruma-identifiers: diesel

Problem Description

Attempting to update ruma-identifiers as of commit 78b0d1e to Rust 2018 and warnings related to Diesel's custom derives make me think it might not be compatible.

What is the expected output?

No warnings.

What is the actual output?

The same error for many similar types deriving FromSqlRow:

warning: cannot find type `EventId` in this scope
  --> src/lib.rs:85:39
   |
85 | #[cfg_attr(feature = "diesel", derive(FromSqlRow))]
   |                                       ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #50504 <https://github.com/rust-lang/rust/issues/50504>

Steps to reproduce

  1. Check out ruma-identifers at commit 78b0d1e.
  2. Run cargo fix --features diesel --edition.
  3. View output.

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)

^ A nightly Rust is required because of the library's use of try_from but the issue being reported is not specific to nightly.

@jimmycuadra
Copy link
Contributor Author

jimmycuadra commented Dec 8, 2018

Here's a link to the Rust issue reported in the warning: rust-lang/rust#50504. It seems the Diesel team (or at least Sean) was already aware of this issue. Maybe now the circumstances have changed since Rust 2018 has shipped and this is now a hard error under the edition.

@jimmycuadra
Copy link
Contributor Author

#1785 also seems related.

@weiznich
Copy link
Member

weiznich commented Dec 8, 2018

That warning is already fixed on master. Release is blocked on getting a review of a few open PR's.

@weiznich weiznich closed this as completed Dec 8, 2018
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

2 participants