Handle setters properly in NameFilter.

Handle setters properly in NameFilter.

According to the language spec (which we are trying to follow as closely
as possible in the implementation of summaries), a setter for `x` has a
name `x=`, hence a combinator like `show x` should show both the name
`x` and `x=`.

This has no immediate effect beyond the unit test for NameFilter (since
at the moment the only names which are affected by the behavior of
NameFilter are the names of classes, and they never end in `=`).  But in
a future CL I plan to use NameFilter to help build public and export
namespaces, and once that lands I will need NameFilter to handle setters
properly.

R=scheglov@google.com

Committed: https://github.com/dart-lang/sdk/commit/927744e318709d002cffa3dc5a1aeb1d60397545

[Paul Berry, 2016-01-11 22:05:55]

paulberry@google.com changed reviewers:
+ brianwilkerson@google.com, scheglov@google.com

[scheglov, 2016-01-11 22:22:04]

LGTM

[Paul Berry, 2016-01-11 22:28:47]

Description was changed from

==========
Handle setters properly in NameFilter.

According to the language spec (which we are trying to follow as closely
as possible in the implementation of summaries), a setter for `x` has a
name `x=`, hence a combinator like `show x` should show both the name
`x` and `x=`.

This has no immediate effect beyond the unit test for NameFilter (since
at the moment the only names which are affected by the behavior of
NameFilter are the names of classes, and they never end in `=`).  But in
a future CL I plan to use NameFilter to help build public and export
namespaces, and once that lands I will need NameFilter to handle setters
properly.
==========

to

==========
Handle setters properly in NameFilter.

According to the language spec (which we are trying to follow as closely
as possible in the implementation of summaries), a setter for `x` has a
name `x=`, hence a combinator like `show x` should show both the name
`x` and `x=`.

This has no immediate effect beyond the unit test for NameFilter (since
at the moment the only names which are affected by the behavior of
NameFilter are the names of classes, and they never end in `=`).  But in
a future CL I plan to use NameFilter to help build public and export
namespaces, and once that lands I will need NameFilter to handle setters
properly.

R=scheglov@google.com

Committed:
https://github.com/dart-lang/sdk/commit/927744e318709d002cffa3dc5a1aeb1d60397545
==========

[Paul Berry, 2016-01-11 22:28:48]

Committed patchset #1 (id:1) manually as
927744e318709d002cffa3dc5a1aeb1d60397545 (presubmit successful).

[Brian Wilkerson, 2016-01-12 00:03:41]

LGTM

[Brian Wilkerson, 2016-01-12 00:03:42]

LGTM