Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…

Related:

• Refinement tracking issue, so you could write a method without the bounds when they aren't met, and actually make use of it
• Trivial bounds tracking issue, so you could write a method with the trivially unmet bounds present without a compiler error

steffahn:

For some reason, rustc doesn’t care so much anymore about “impossible” bounds if you add some higher-ranked…