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
{{ message }}
Repository navigation
[1.30 beta] Unresolved import errors in a few crates #54471
Some crates are failing in 1.30 beta with errors like this one:
error[E0432]: unresolved import `geometry::Isometry`
--> /cargo-home/registry/src/github.com-1ecc6299db9ec823/nalgebra-0.15.3/src/base/cg.rs:15:16
|
15 | use geometry::{Isometry, IsometryMatrix3, Orthographic3, Perspective3, Point, Point3, Rotation2,
| ^^^^^^^^ no `Isometry` in `geometry`. Did you mean to use `isometry`?
The ipfs-api crate does not use nlagebra at all. All of these build logs seem to have something wrong with serde involved; for example, ipfs-api gets a lot of errors associated with its use of #[serde(rename_all = "PascalCase")], along the lines of:
Sep 21 17:09:54.166 INFO kablam! error: cannot determine resolution for the attribute macro `serde`
Sep 21 17:09:54.166 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/nalgebra-0.15.3/src/linalg/symmetric_tridiagonal.rs:16:5
Sep 21 17:09:54.166 INFO kablam! |
Sep 21 17:09:54.166 INFO kablam! 16 | serde(
Sep 21 17:09:54.166 INFO kablam! | ^^^^^
Sep 21 17:09:54.166 INFO kablam! |
Sep 21 17:09:54.166 INFO kablam! = note: import resolution is stuck, try simplifying macro imports
All the other build logs appear to have "undefined type or module" along with the error import resolution is stuck, try simplifying macro imports. Removing the serde annotations from ipfs-api lets it build successfully, though the protocol it speaks is then incorrect.
Yes, ipfs-api is a separate case (probably with the same underlying issue in rustc) and it's already tracked separately in #54386, the other regressed crates use nalgebra.
#![allow(unused)]#[macro_use]externcrate serde_derive;useself::one::*;useself::two::*;mod serde {}mod one {use serde;#[derive(Serialize)]#[serde]structOne;}mod two {use serde;#[derive(Serialize)]#[serde]structTwo;}fnmain(){}
Activity
petrochenkov commentedon Sep 23, 2018
The root issue is in the
nalgebracrate and it's something that was fixed betweennalgebra 0.16.0andnalgebra 0.16.1.EDIT:
nalgebra 0.16.1removeduse serde;imports, almost certainly as a response to this regression.icefoxen commentedon Sep 23, 2018
The
ipfs-apicrate does not usenlagebraat all. All of these build logs seem to have something wrong withserdeinvolved; for example,ipfs-apigets a lot of errors associated with its use of#[serde(rename_all = "PascalCase")], along the lines of:All the other build logs appear to have "undefined type or module" along with the error
import resolution is stuck, try simplifying macro imports. Removing theserdeannotations fromipfs-apilets it build successfully, though the protocol it speaks is then incorrect.petrochenkov commentedon Sep 23, 2018
Yes,
ipfs-apiis a separate case (probably with the same underlying issue in rustc) and it's already tracked separately in #54386, the other regressed crates usenalgebra.icefoxen commentedon Sep 23, 2018
Aha, thanks!
petrochenkov commentedon Sep 23, 2018
Minimized:
petrochenkov commentedon Sep 24, 2018
Fixed in #54518
All the crates listed in #54471 (comment) build successfully now.
Rollup merge of rust-lang#54518 - petrochenkov:regr130, r=alexcrichton