问题描述
我有一些方法和类会导致验证程序因内存不足而失败。如果不是因为它导致所有验证停止甚至丢失到目前为止发现的警告而不是输出它们，那就没关系。
I have a handful of methods and classes that cause the verifier to fail by going out of memory. That would be fine, if it weren't for the fact that it causes all verification to stop and even loses the warnings found so far instead of outputting them.
我认为应该采取一些策略在这里使用：
I think a couple strategies should be used here:
- 在找到时输出警告，或者至少在以已知方式失败时输出警告。
- Output warnings as they are found, or at least output them when failing in known ways.
- 继续下一步方法验证，即使方法验证失败。
- Continue to the next method verification even if the verification of a method fails.
- 输出一个警告或错误，说明验证者失败的地方，而不是只在构建输出中。
- Output a warning or an error saying where the verifier failed, instead of only having it in the build output.
推荐答案
对不起OOM问题。感谢您的建议，我们将研究它们。对于1st，您可以通过添加选项"-sortwarns = false"来启用验证程序以急切地发出警告。我们没有这样做的原因是因为我们内部
对警告进行排名，所以要在列表中列出最高相关性。
sorry for the OOM problem. Thank you for the suggestions, we will look into them. As for the 1st, you can enable the verifier to eagerly emit the warnings is by adding the option "-sortwarns=false". The reason we are not doing it is because we internally rank the warnings, so to put higher in the list the most relevants.
Ciao，
f
这篇关于建议：更优雅地处理内存不足的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！