In that case, just mark it with `@deprecated`. We promised not to remove APIs in a release that have not been deprecated in a prior one. Hence, this can be deprecated in 0.4, and removed once we start the 0.5 cycle.

We follow the following deprecation style: 

 1. Mark the class as @deprecated with a Java annotation.
 2. Mark it as `@Deprecated` in the JavaDocs with a comment to a version it was deprecated in and the remedy. For example `@Deprecated in 0.4. Please use the other constructor instead or rely on Tang for defaults`