mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
standardize naming of tuples and tuple patterns on "elements".
Previously some parts of the compiler referred to them as "fields", and most referred to them as "elements". Use the more generic 'elements' nomenclature because that's what we refer to other things in the compiler (e.g. the elements of a bracestmt). At the same time, make the API better by providing "getElement" consistently and using it, instead of getElements()[i]. NFC. Swift SVN r26894
This commit is contained in:
@@ -530,7 +530,7 @@ AggregateAvailableValues(SILInstruction *Inst, SILType LoadTy,
|
||||
if (TupleType *TT = LoadTy.getAs<TupleType>()) {
|
||||
SmallVector<SILValue, 4> ResultElts;
|
||||
|
||||
for (unsigned EltNo : indices(TT->getFields())) {
|
||||
for (unsigned EltNo : indices(TT->getElements())) {
|
||||
SILType EltTy = LoadTy.getTupleElementType(EltNo);
|
||||
unsigned NumSubElt = getNumSubElements(EltTy, M);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user