减少将原始类型与泛型一起使用时减少潜在的垃圾浪费吗？

Firstly, I would like to say I am a bit confused by your mention of "garbage issues", because your context is not entirely clear whether you're referring to Java's implicit garbage collection of runtime memory or whether you're concerned about this registration data is piling up somewhere else, like a database.

If you're referring to Java's runtime memory management: Java is (as you probably know) automatically garbage collected but you can suggest (with no guarantee whatsoever) Java to collect garbage at any time with System.gc(). This is almost always a micro-optimization and provides little to no real benefit as Java is already amazing at determining the correct time to do garbage collection without you. I wouldn't even bother worrying about it in Java.

如果您指的是这种数据存储的外部模型，我会很担心。由于缺乏更好的术语，采用抽象的“ setter”方法可以使错误或副作用暴露在内存中。这需要在Java实现上进行双重管理，以使其尽可能避免出现错误，但是您还需要自己管理外部存储中的内存。

尽管如此，几乎可以肯定，这种情况表明支持代码需要重组和更多指导。我认为，这种抽象设置方法是一种代码气味。