well the difference in groovy I think is that groo...
# gradle
x
well the difference in groovy I think is that groovy somehow is evaluating it later, somehow it's much more eagerly evaluated by kotlin instead of only being evaluated when I do a
gradle publish
g
I think that groovy doesn’t care about nullability and saves no to non-nullable field
And this configuration is not lazy in groovy
x
could be
I don't know enough about it honestly
g
Groovy and Kotlin work similar here, kotlin just doesn’t allow you to assign null to non-nullable property