Deprecate mutable aspects of MethodParameter #23385
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Issue #23352 has shown that the mutable nature of
MethodParameter
can cause problems. One particularly unusual aspect is thatgetContainingClass()
can change as a side effect of callingGenericTypeResolver.resolveParameterType()
.Internally, we don't actually mutate
MethodParameter
instances that often so it's possible that we could deprecate the mutation methods in favor of calls that return a new instance.The text was updated successfully, but these errors were encountered: