Make SearchMatch usable for the new index - remove the element field.

Make SearchMatch usable for the new index - remove the element field.

The 'element' is still accessible, but as a computed property.

In many cases we don't need to know the containing element, and need
only the unit source, or the LibraryElement. So, by computing it on
demand we may save some time and make SearchMatch usable with the
new index - where we don't know the Element.

R=brianwilkerson@google.com
BUG=

Committed: https://github.com/dart-lang/sdk/commit/80531d974dff8e9b3b69ceb70beaed6ebd691681

[Brian Wilkerson, 2016-03-03 14:59:17]

LGTM

[scheglov, 2016-03-03 16:41:00]

Description was changed from

==========
Make SearchMatch usable for the new index - remove the element field.

The 'element' is still accessible, but as a computed property.

In many cases we don't need to know the containing element, and need
only the unit source, or the LibraryElement. So, by computing it on
demand we may save some time and make SearchMatch usable with the
new index - where we don't know the Element.

R=brianwilkerson@google.com
BUG=
==========

to

==========
Make SearchMatch usable for the new index - remove the element field.

The 'element' is still accessible, but as a computed property.

In many cases we don't need to know the containing element, and need
only the unit source, or the LibraryElement. So, by computing it on
demand we may save some time and make SearchMatch usable with the
new index - where we don't know the Element.

R=brianwilkerson@google.com
BUG=

Committed:
https://github.com/dart-lang/sdk/commit/80531d974dff8e9b3b69ceb70beaed6ebd691681
==========

[scheglov, 2016-03-03 16:41:01]

Committed patchset #1 (id:1) manually as
80531d974dff8e9b3b69ceb70beaed6ebd691681 (presubmit successful).