Explore >> Select a destination
|
You are here 
|
mydeveloperplanet.com | ||
| | | | |
ryanharter.com
|
|
| | | | | Value types in Java are hard. Well, not hard, but tedious. Google's AutoValue library makes them much easier and has just received the long awaited update that adds the flexibility of extensions. Value Types in Java Before we can talk about how great AutoValue is, let's look at the problem it solves: value types. A value type is simply an immutable objects whose equality is based on property values, as opposed to identity. | |
| | | | |
ryanharter.com
|
|
| | | | | In my last article, I gave a basic introduction to AutoValue, the code generating annotation processor that makes immutable value types in Java easy. Now I'd like to take a bit of a deeper look at AutoValue and how it works. Compile Time Annotation Processing First things first, AutoValue is a compile time annotation processor. This means that it only runs when you compile your code, as opposed to when your app is running. | |
| | | | |
www.stackchief.com
|
|
| | | | | What software engineers need to know about Java 17 including new features, deprecated features, and removed functionality. | |
| | | | |
www.smashcompany.com
|
|
| | | |||
