Proguard吃了我的Object.wait（）(Proguard ate my Object.wait())

 我刚刚发现ProGuard删除了一个.wait（）调用，我用来同步线程，导致竞争条件导致一天的调试快乐:)无论如何...... 
 
 我将其跟踪到以下部分的proguard配置： 
 
-assumenosideeffects public class android.util.Log {
    <methods>;
}
 
 我想知道为什么会这样。 我不确定为什么假设删除Log类没有副作用导致在不同的类/对象上删除.wait（）。 
 
 我看到ProGuard优化也删除了#wait（）调用 ，其中Eric解释说可能会发生这样的事情。 但是，他没有解释原因。 
 
 另外，我在这里找到了如何删除Logs的示例（ http://proguard.sourceforge.net/index.html#manual/examples.html ）。 所以，我可以替换这个配置程序（但这不是这个问题的重点）。 

I just found that ProGuard removed a .wait() call which I used to synchronize threads, which lead to a race condition which lead to a day of happy debugging :) Anyway...
 
I tracked it down to following piece of proguard configuration:
 
-assumenosideeffects public class android.util.Log {
    <methods>;
}
 
I want to understand WHY this happened. I am not sure why assuming that removal of Log class has no side effects leads to removal of .wait() on different class/object.
 
I saw ProGuard optimization also remove #wait() calls where Eric explains that such things may happen. However, he doesn't explain why.
 
Also, I found example how to remove Logs here (http://proguard.sourceforge.net/index.html#manual/examples.html). So, I can replace this piece of proguard of configuration (but it's not the point of this question).

原文：https://stackoverflow.com/questions/16846691