Changeset 218218 in webkit for trunk/Source/JavaScriptCore/bytecode/PropertyCondition.cpp
- Timestamp:
- Jun 13, 2017, 3:39:34 PM (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/JavaScriptCore/bytecode/PropertyCondition.cpp
r218203 r218218 48 48 return; 49 49 case Absence: 50 case AbsenceOfSet ter:50 case AbsenceOfSetEffect: 51 51 out.print(" with prototype ", inContext(JSValue(prototype()), context)); 52 52 return; … … 125 125 } 126 126 127 case AbsenceOfSet ter: {127 case AbsenceOfSetEffect: { 128 128 if (structure->isDictionary()) { 129 129 if (verbose) … … 135 135 PropertyOffset currentOffset = structure->getConcurrently(uid(), currentAttributes); 136 136 if (currentOffset != invalidOffset) { 137 // FIXME: Given the addition of the check for ReadOnly attributes, we should refactor138 // instances of AbsenceOfSetter.139 // https://bugs.webkit.org/show_bug.cgi?id=173322 - Refactor AbsenceOfSetter to something like AbsenceOfSetEffects140 137 if (currentAttributes & (ReadOnly | Accessor | CustomAccessor)) { 141 138 if (verbose) { … … 224 221 // Currently we assume that an impure property can cause a property to appear, and can also 225 222 // "shadow" an existing JS property on the same object. Hence it affects both presence and 226 // absence. It doesn't affect AbsenceOfSet terbecause impure properties aren't ever setters.223 // absence. It doesn't affect AbsenceOfSetEffect because impure properties aren't ever setters. 227 224 switch (m_kind) { 228 225 case Absence: … … 355 352 out.print("Absence"); 356 353 return; 357 case JSC::PropertyCondition::AbsenceOfSet ter:354 case JSC::PropertyCondition::AbsenceOfSetEffect: 358 355 out.print("Absence"); 359 356 return;
Note:
See TracChangeset
for help on using the changeset viewer.