Lines Matching refs:your

13 Avoid mutable types, including arrays, for your properties, especially if you
14 make your accessor methods `public`. The generated accessors don't copy the
15 field value on its way out, so you'd be exposing your internal state.
17 Note that this doesn't mean your factory method can't *accept* mutable types as
36 You should essentially *never* need an alternative implementation of your
38 framework. If your behavior has enough complexity (or dependencies) that it
47 reference from your source code: the call from your static factory method to the
55 Consider that other developers will try to read and understand your value class
56 while looking only at your hand-written class, not the actual (generated)
57 implementation class. If you mark your concrete methods `final`, they won't have
64 …your abstract class. It prevents unwanted subclasses, and prevents an undocumented public construc…