Skip to content

regression: trait bound not satisfied #103243

Activity

  1. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    E-needs-bisectionCall for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc
    on Oct 19, 2022
  2. added this to the 1.65.0 milestone on Oct 19, 2022
  3. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Oct 19, 2022
  4. compiler-errors commented on Oct 19, 2022

    @compiler-errors
    Contributor

    This regressed in #98900, cc @lcnr - I may take a look at this later today.

  5. removed
    E-needs-bisectionCall for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc
    on Oct 19, 2022
  6. compiler-errors commented on Oct 19, 2022

    @compiler-errors
    Contributor

    The regression in diesel-softdelete is separate and regressed in #100757 cc @ouz-a

  7. compiler-errors commented on Oct 20, 2022

    @compiler-errors
    Contributor

    I minimized this from path-planning:

    pub trait CSpace<const N: usize>: Sized {
        type Traj;
    }
    
    pub trait FullTrajectory<T, S1, const N: usize> {}
    
    pub struct Const<const R: usize>;
    
    pub trait Obstacle<CS, const N: usize>
    where
        CS: CSpace<N>,
    {
        fn trajectory_free<FT, S1>(&self, t: &FT)
        where
            FT: FullTrajectory<CS::Traj, S1, N>;
    }
    
    // -----
    
    const N: usize = 4;
    
    struct ObstacleSpace2df32;
    
    impl<CS> Obstacle<CS, N> for ObstacleSpace2df32
    where
        CS: CSpace<N>,
    {
        fn trajectory_free<TF, S1>(&self, t: &TF)
        where
            TF: FullTrajectory<CS::Traj, S1, N>,
        {}
    }
  8. compiler-errors commented on Oct 20, 2022

    @compiler-errors
    Contributor

    I put up a potential fix in #103279

  9. apiraino commented on Oct 20, 2022

    @apiraino
    Contributor

    WG-prioritization assigning priority (Zulip discussion).

    @rustbot label -I-prioritize +P-critical

  10. added and removed
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Oct 20, 2022
  11. added a commit that references this issue on Oct 26, 2022
  12. compiler-errors commented on Nov 3, 2022

    @compiler-errors
    Contributor

    1.65 is released

  13. added a commit that references this issue on Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P-criticalCritical priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions