- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Gill (0.14 sec)
-
CONTRIBUTING.md
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. [APIs]: https://en.wikipedia.org/wiki/Application_programming_interface [issue]: https://github.com/google/guava/issues
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
For any non-trivial change, we need to be able to answer these questions: * Why is this change done? What's the use case? * For user facing features, what will the API look like? * What test cases should it have? What could go wrong? * How will it roughly be implemented? We'll happily provide code pointers to save you time.
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
TensorFlow team members will be assigned to review your pull requests. Once the pull requests are approved and pass continuous integration checks, a TensorFlow team member will apply `ready to pull` label to your change. This means we are working on getting your pull request submitted to our internal repository. After the change has been submitted internally, your pull request will be merged automatically on GitHub.
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)