You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
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.
Versions
Feature Flags
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
:Steps to reproduce
cargo fix --features diesel --edition
.Checklist
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.The text was updated successfully, but these errors were encountered: