Explore >> Select a destination
|
You are here 
|
endoflineblog.com | ||
| | | | |
tomasvotruba.com
|
|
| | | | | I'm currently working as Rector consultant for [Spaceflow](https://spaceflow.io/en), Prague-based rising startup with very nice codebase. One of the pre-requisites for Rector is to have code that static analyser can work with. PHPStan that Rector uses depends on `@var` annotations and not every property had that. Well... **over 2500 of them**. I'll show you how we completed them without any manual change of the code and how you can do the same... today. | |
| | | | |
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. | |
| | | | |
jensrantil.github.io
|
|
| | | | | Business contract testing is much simpler done by method calls instead of using something like PACT. | |
| | | | |
blog.sigplan.org
|
|
| | | Working through a programming exercise, we see that Lisps Code is data philosophy is a natural enabler for program synthesis. | ||
