Page MenuHomePhabricator

Improvements to `LINT_IMPLICIT_VISIBILITY`
ClosedPublic

Authored by joshuaspence on Jan 7 2015, 1:26 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 21, 3:42 PM
Unknown Object (File)
Sat, Nov 16, 6:16 PM
Unknown Object (File)
Sat, Nov 9, 11:39 PM
Unknown Object (File)
Sat, Nov 9, 10:36 PM
Unknown Object (File)
Oct 18 2024, 10:08 AM
Unknown Object (File)
Oct 9 2024, 2:04 PM
Unknown Object (File)
Oct 9 2024, 2:04 PM
Unknown Object (File)
Oct 9 2024, 2:04 PM
Subscribers

Details

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

joshuaspence retitled this revision from to Improvements to `LINT_IMPLICIT_VISIBILITY`.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
richardvanvelzen edited edge metadata.

Seems reasonable to me.

One minor question - should it be:

  1. static public function or public static function
  2. abstract public function or public abstract function

?
For 1. I prefer the latter, while for 2. I prefer the former.

However, I don't care either way. This looks fine.

I think we use public static (vs static public) and abstract public (vs public abstract) nearly 100% of the time, although leaving the order undefined also seems fine to me.

epriestley edited edge metadata.
This revision is now accepted and ready to land.Jan 7 2015, 2:20 PM

I actually have a lint rule coming up for LINT_MODIFIER_ORDERING.

This revision was automatically updated to reflect the committed changes.