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
We have standard boiler plate for internal classes which are public which reads:
* <p>This class is internal and is hence not for public use. Its APIs are unstable and can change
* at any time.
But I wonder if we should adjust our boilerplate for these types of methods - internal because we make no compatibility guarantees, but acceptable for public consumption provided the user accepts the risks of breaking changes.
Maybe something like:
This class is internal and experimental. Its APIs are unstable and can change at any time. Its APIs (or a version of them) may be promoted to the public stable API in the future, but no guarantees are made.
We have standard boiler plate for internal classes which are public which reads:
But I wonder if we should adjust our boilerplate for these types of methods - internal because we make no compatibility guarantees, but acceptable for public consumption provided the user accepts the risks of breaking changes.
Maybe something like:
Places this updated message would be relevant:
Originally posted by @jack-berg in #6367 (comment)
The text was updated successfully, but these errors were encountered: