You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can confirm that this bug only affects Eclipse. Likely cause: lombok.eclipse.handlers.HandleConstructor.fieldsNeedingExplicitDefaults() does not check for initializing expression, but lombok.javac.handlers.HandleConstructor.fieldsNeedingExplicitDefaults() does (line 401).
With Lombok 1.18.2, the following class produces a compiler error on the
@NoArgsConstructor
annotation stating the final fieldfoo
cannot be assigned:On the command line the project compiles properly. Shouldn't the generated no-arg constructor simply skip the initialized, final field?
The text was updated successfully, but these errors were encountered: