Remove type flag based opaque type workaround
This commit is contained in:
parent
84fc551664
commit
58c08cd037
9 changed files with 30 additions and 181 deletions
|
|
@ -204,14 +204,6 @@ bitflags! {
|
|||
| TypeFlags::HAS_CT_INFER.bits
|
||||
| TypeFlags::HAS_TY_PLACEHOLDER.bits
|
||||
| TypeFlags::HAS_CT_PLACEHOLDER.bits
|
||||
// The `evaluate_obligation` query does not return further
|
||||
// obligations. If it evaluates an obligation with an opaque
|
||||
// type, that opaque type may get compared to another type,
|
||||
// constraining it. We would lose this information.
|
||||
// FIXME: differentiate between crate-local opaque types
|
||||
// and opaque types from other crates, as only opaque types
|
||||
// from the local crate can possibly be a local name
|
||||
| TypeFlags::HAS_TY_OPAQUE.bits
|
||||
// We consider 'freshened' types and constants
|
||||
// to depend on a particular fn.
|
||||
// The freshening process throws away information,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue