add comment explaining why ty_and_layout_field is not used
Co-authored-by: Jack Wrenn <me@jswrenn.com>
This commit is contained in:
parent
e023590de4
commit
85f01386da
1 changed files with 4 additions and 1 deletions
|
@ -495,7 +495,10 @@ pub(crate) mod rustc {
|
|||
(ty, layout): (Ty<'tcx>, Layout<'tcx>),
|
||||
i: FieldIdx,
|
||||
) -> Ty<'tcx> {
|
||||
// FIXME: Why does this not just use `ty_and_layout_field`?
|
||||
// We cannot use `ty_and_layout_field` to retrieve the field type, since
|
||||
// `ty_and_layout_field` erases regions in the returned type. We must
|
||||
// not erase regions here, since we may need to ultimately emit outlives
|
||||
// obligations as a consequence of the transmutability analysis.
|
||||
match ty.kind() {
|
||||
ty::Adt(def, args) => {
|
||||
match layout.variants {
|
||||
|
|
Loading…
Add table
Reference in a new issue