|
You are here |
msfjarvis.dev | ||
| | | | |
initialcommit.com
|
|
| | | | | Every instance of a class has its own state and behavior, whenever the state of a particular instance is modified, other instances are not affected. | |
| | | | |
initialcommit.com
|
|
| | | | | An object is immutable if its state cannot change after construction, immutable objects don't expose any way for other objects to modify their state, the object's fields are initialized only once inside the constructor and never change again. | |
| | | | |
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. | |
| | | | |
andreabergia.com
|
|
| | | This post is part of the Writing a JVM in Rust series. I have written a JVM in Rust ?thispost A JVM in Rust part 2 - The class files format A JVM in Rust part 3 - Parsing class files A JVM in Rust part 4 - The Java bytecode A JVM in Rust part 5 - Executing instructions A JVM in Rust part 6 - Methods and exceptions A JVM in Rust part 7 - Objects and GC A JVM in Rust part 8 - Retrospective Lately Ive been spending quite a bit of time learning Rust, and as any sane person would do, after writing a few 100 ... | ||