Lines Matching refs:AutoValue

4 This page answers common how-to questions that may come up when using AutoValue
5 **with the builder option**. You should read and understand [AutoValue with
50 @AutoValue
59   @AutoValue.Builder
70 Use whichever names you like; AutoValue doesn't actually care.
94 @AutoValue
104   @AutoValue.Builder
126 your abstract builder type, to your value class. AutoValue will implement it.
141 @AutoValue
156   @AutoValue.Builder
175 *   the non-visible, abstract method that AutoValue implements
183 @AutoValue
192   @AutoValue.Builder
215 @AutoValue
224   @AutoValue.Builder
258 @AutoValue
267   @AutoValue.Builder
297 If you use the builder option, AutoValue will not generate a visible constructor
319 @AutoValue
327   @AutoValue.Builder
347 collections] to make that explicit. AutoValue's builder support includes a few
356 construct `ImmutableSet` instances to pass into your builder. So AutoValue
366 @AutoValue
376   @AutoValue.Builder
397 @AutoValue
407   @AutoValue.Builder
457 @AutoValue
467   @AutoValue.Builder
508 Often a property of an `@AutoValue` class is itself an immutable class,
509 perhaps another `@AutoValue`. In such cases your builder can expose a builder
516 @AutoValue
525   @AutoValue.Builder
533 @AutoValue
542   @AutoValue.Builder
563 Although the nested class in the example (`Species`) is also an `@AutoValue`
583   that accepts an argument of type `Species`. This is how AutoValue handles