Currently those typedef classes are deleted during the platform build to avoid incurring any system image cost at all. We're hoping to get the dex tool to be able to strip out annotations like these; when that happens we should be able to leave them around and make it easier to pass on typedefs to downstream code.
-- Tor On Mon, Aug 4, 2014 at 12:24 PM, Jake Wharton <[email protected]> wrote: > Will libraries and the platform be exposing @IntDef-annotation > annotations publicly? > > Ideally the standalone libraries would ship the annotations as nested > classes (e.g., RecyclerView.ScrollState) and annotate their getters and > setters. This way we can avoid problems like this in downstream code: > > I’m not sure the right approach for the platform. Ideally it would also > ship with these so we can leverage the same static analysis. > > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
