用Lombok生成Java getter / setter以获得带注释的代码(Java getter/setter generation with Lombok for code with annotations)

 据我所知，这只是指出内存中重复的字符串。 但是，这不仅仅用于找到相同字符串已被输入到多个资源的情况。 例如，由于字符串在Java中是不可变的，因此您最终可能会得到比您最初意识到的更多的字符串实例。 如果你的应用程序有很多字符串连接代码，但不使用StringBuilder，或者如果你的应用程序进行任何字符串/文本处理，它很容易以字符串占用意想不到的大量空间。 但相反，为了获得一些空间（一旦你能看到问题出在哪里），通常可以进行相对容易的优化。 所以你可以说这个任务更多的是关于记忆的“优化”，而不是找到泄漏。 

As far as I know, this does just point out duplicated strings in memory. However, this is useful for more than just finding cases where the same string has been entered into more than one resource. For example, as Strings are immutable in Java, you can easily end up with many more instances of strings than you might initially realise. If your app has lots of string concatenation code but dont use StringBuilder, or if your app does any string/text processing, its fairly easy to end up with unexpectedly large amounts of space taken up by strings. But conversely, it can often be a relatively easy optimization to make in order to gain back some space (once you can see what the problem is). So you could say this task is more about memory 'optimization', rather than finding a leak.