Skip to content

Automatic edition migration broken for diesel. #136345

Open
@weiznich

Description

I tried this code:

diesel-rs/diesel@1c5cf1c

and followed the setups outlined here to test migrating to the 2024 edition.

I expected to see this happen: Migration succeeds
Instead, this happened: I get the following compiler errors: Gist link as the log is too large to even post it inline
I did not investigate why which error happens, but it seems like that there is again something strange going on with feature unification, as otherwise you wouldn't end up with this kind of error messages that mix different backend types like this.

I also want to highlight that this is now the third edition in row that breaks diesel and that requires significant manual migration effort on our side. At least for me that doesn't uphold the promises made by various edition RFC's and team members.

Meta

rustc --version --verbose:

rustc 1.85.0-beta.6 (14445aaf3 2025-01-26)
binary: rustc
commit-hash: 14445aaf35d45f62fddda8cb5027f44ba4316e7f
commit-date: 2025-01-26
host: x86_64-unknown-linux-gnu
release: 1.85.0-beta.6
LLVM version: 19.1.7

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: This is a bug.E-needs-investigationCall for partcipation: This issues needs some investigation to determine current statusE-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleT-cargoRelevant to the cargo team, which will review and decide on the PR/issue.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions