Hint when @protected members are used outside instances of subclasses.

[pq]

See @protectedannotation definition here: https://codereview.chromium.org/1719353002/.

[pq]

Support for methods landed in 84f32fe.
Support for members, in general, landed in 212a058.

[Hixie]

qv #3193, #6119

[pq]

meta package published. Closing out.

[donny-dont]

@pq is the analyzer package going to get a push as well with this? I didn't see the protected checks in 0.27.3-alpha.0

[bwilkerson]

Eventually, yes. We're in the process of implementing several annotations and it might make sense to wait for more of them to be implemented rather than flooding the world with lots of extra versions.

Do you need it for something?

[donny-dont]

@bwilkerson I can certainly wait. Been waiting a long time for @protected so whats a little longer. Great work all around 👍

[bwilkerson]

I guess the question really is, do you need a version of the analyzer package published to pub, or are you just waiting for a new build of the SDK with this support in it? (The two are not necessarily kept in sync.)

[donny-dont]

I have a library that will load a library through the analyzer then gather the metadata and then let you run queries against the data. I have support for deprecated and override and I was going to add support for instantiating @protected whenever that lands.

[bwilkerson]

It isn't clear that you need a new version of the analyzer package. Analyzer doesn't need to understand an annotation to capture it (though it does have some utility methods for the annotations it knows about). And the annotation itself is defined in the 'meta' package (https://pub.dartlang.org/packages/meta), so you can start adding it to code today. You probably have enough to do what you want, although the utility methods would be helpful.

[donny-dont]

It was the utility methods ala isDeprecated that would be nice. No rush on my end.