Age | Commit message (Collapse) | Author |
|
hashCode method as final if it isn’t modified. This doesn’t change its behavior whatsoever, but some linters and especially eclipse save actions (specifically: ‘mark local variables final if possible’) cause issues when they try to mess with generated code. Of course, now any save action with ‘remove useless modifiers’ would cause an issue but those don’t (yet…) exist.
|
|
in JDK12-preview javac.
|
|
|
|
in the face of already present ones.
|
|
super.
|
|
trickery to compile straight from jar to jar, messing up our wrapper around javac’s javaFileObject. Bug report and suggested fix from external sources, we didn’t test it, but we only kick in this alternative if an exception occurs, so it couldn’t possibly affect anything that was already working fine. See PR #1929
|
|
actual handwritten type.
|
|
does by hand and lombok fills in whatever is missing.
|
|
|
|
|
|
|
|
overzealous as to what it marks as ‘generated’, if you manually write the builder class and add some elements, you’d get crazy errors on those.
|
|
janrieke-wildcardsSingularFix
|
|
reflective access via a class that uses sun.misc.Unsafe to arrange access. From the nqzero permit-reflect library.
|
|
|
|
Added Spring NonNull and Nullable annotations
|
|
Customizable SuperBuilder
|
|
|
|
way javac/java support it.
|
|
(module-info) style projects.
|
|
|
|
|
|
|
|
longer throws NPE.
|
|
|
|
|
|
|
|
janrieke-superToBuilder
|
|
testing that the compiler emits warning/error messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and for example their use on the typearg in a collection type which is being `@Singular`-ized.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
‘copyable’ annotations get copied’, with ‘copyable’ defined as a specific FQN-style list of well-known nullity-indicating annotations, plus whatever you configured in lombok.config.
Also some work on the notion of TYPE_USE annotations.
|
|
|
|
|
|
|