- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for featured (0.2 sec)
-
CONTRIBUTING.md
We make changes to Guava's public [APIs][], including adding new APIs, very carefully. Because of this, if you're interested in seeing a new feature in Guava, the best approach is to create an [issue][] (or comment on an existing issue if there is one) requesting the feature and describing specific use cases for it. If the feature has merit, it will go through a thorough process of API design and review. Any code should come after this.
Plain Text - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 3.7K bytes - Viewed (0) -
CONTRIBUTING.md
* Create integration tests that exercise a Gradle build for the bug/feature. * Annotate tests that correspond to a bug on GitHub (`@Issue("https://github.com/gradle/gradle/issues/2622")`). * Add documentation to the User Manual and DSL Reference (under [platforms/documentation/docs/src/docs](platforms/documentation/docs/src/docs/)).
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat May 04 07:43:02 GMT 2024 - 15.6K bytes - Viewed (0) -
CONTRIBUTING.md
* When you contribute a new feature to TensorFlow, the maintenance burden is (by default) transferred to the TensorFlow team. This means that the benefit of the contribution must be compared against the cost of maintaining the feature. * Full new features (e.g., a new op implementing a cutting-edge algorithm) typically will live in
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0)