The instantiationAware and smartInstantiationAware of BeanPostProcessorCache are not exactly equal. Using hasSmartInstantiationAwareBeanPostProcessors() to replace hasInstantiationAwareBeanPostProcessors() before using smartInstantiationAware can not only optimize the code, but also clarify the semantics.
Comment From: pivotal-cla
@supalle Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@supalle Thank you for signing the Contributor License Agreement!
Comment From: snicoll
@supalle it's really hard to make up our mind based on the proposal as it doesn't have any test that illustrates what you mean by clarifying the semantics. Can you please clarify?
Comment From: supalle
有点久远了，我重新看了一下，问题不大，无伤大雅。