Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 5
    To my understanding, the different "copyOf​" overloads shown in the example are part of the same system concept. I would actually would have expected them to be implemented only once with Java's generics - but I guess that API exists longer than Java has generics, and the performance impact using generics for an API which is intended to provide a blazingly fast copy function would not be acceptable for lots of scenarios. Commented Jun 24, 2021 at 8:34
  • @DocBrown I agree that for a generic method it would be reasonable to have a single piece of documentation for the method. However, I think the code and the documentation range over different systems. This is subtle, but I think what constitutes a system concept in the code and what constitutes a system concept in the documentation of that code differ. In this case the language limitations of java resulted in multiple similar methods being required to express a single domain-system concept, which in turn has given rise to multiple separate code-system concepts in the documentation. Commented Jun 24, 2021 at 8:56