a669f440a6
Reason: causes Flutter analysis performance regression. https://github.com/flutter/flutter/issues/68716 We will get back to applying resolution after loading AST when we switch to the binary format, and so recover enough performance. WIP for it: https://dart-review.googlesource.com/c/sdk/+/168260 Unfortunately this means that it will get even bigger. Revert "Separate AST from resolution (per declaration)." This reverts commit4d6fba37de. Revert "Remove commented out code from LinkedUnitContext." This reverts commitc4f2c8ec3e. Revert "Issue 43890. Implement applying resolution to IndexExpression." This reverts commit088524efa6. Revert "Issue 43888. Fix for applying resolution to PropertyAccess in cascade." This reverts commit1f660a7acf. Change-Id: I808c1fc62161458d7544d7741e4b358c99b0b55f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/168881 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>