Oh, I knew about all-open, so now there's another one specific for Spring? Okay, I'll have a second look at it.
Well it's a very unfortunate combination of Kotlin doing its thing, and Spring doing its thing. Plus, Spring should throw an exception if this case is encountered (code simply breaks if it is final, this is not a use case that needs to be preserved). But in general I agree: bytecode generation has a bad smell to it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Oh, I knew about
all-open, so now there's another one specific for Spring? Okay, I'll have a second look at it.Well it's a very unfortunate combination of Kotlin doing its thing, and Spring doing its thing. Plus, Spring should throw an exception if this case is encountered (code simply breaks if it is
final, this is not a use case that needs to be preserved). But in general I agree: bytecode generation has a bad smell to it.