You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was reviewing the source code for delegatingByGVKCache, I found it difficult to quickly determine which interfaces this type implements. I had to examine the methods and their return values to understand the implemented interfaces. Since delegatingByGVKCache doesn't have an explicit constructor, we can't infer the implemented interfaces from the return semantics of the constructor.
Therefore, I would like to propose adding interface assertions to the delegatingByGVKCache type, as follows:
This feature may not be essential, but it would certainly improve the user experience when reviewing the source code, as it allows for quick identification of the interfaces that the type implements. (At least this can be done without the IDE, and you can quickly learn about its implementation interface.)
The text was updated successfully, but these errors were encountered:
When I was reviewing the source code for
delegatingByGVKCache
, I found it difficult to quickly determine which interfaces this type implements. I had to examine the methods and their return values to understand the implemented interfaces. SincedelegatingByGVKCache
doesn't have an explicit constructor, we can't infer the implemented interfaces from the return semantics of the constructor.Therefore, I would like to propose adding interface assertions to the delegatingByGVKCache type, as follows:
This feature may not be essential, but it would certainly improve the user experience when reviewing the source code, as it allows for quick identification of the interfaces that the type implements. (At least this can be done without the IDE, and you can quickly learn about its implementation interface.)
The text was updated successfully, but these errors were encountered: