The current name was opted for before inclusion of singleton methods came into consideration. Now to be on pare with SINGLETON_METHOD_ALIASES, it would be better to opt for INSTANCE_METHOD_ALIASES.
That might require to also rework a bit tests, as they directly call these constants. It goes hand in hand with #10 on that points, the API of the library should be reworked to give public access to these information only through dedicated methods, or even not at all, as they are mostly internal implementation details.
The current name was opted for before inclusion of singleton methods came into consideration. Now to be on pare with
SINGLETON_METHOD_ALIASES
, it would be better to opt forINSTANCE_METHOD_ALIASES
.That might require to also rework a bit tests, as they directly call these constants. It goes hand in hand with #10 on that points, the API of the library should be reworked to give public access to these information only through dedicated methods, or even not at all, as they are mostly internal implementation details.