问题描述
/是否有完整的优化列表优化 C# 编译器密钥 随处可用?
为什么默认禁用?是否值得在实际应用中使用? -- 默认情况下，它仅在 Debug 配置中禁用，在 Release 中启用.
Why is it disabled by default? Is it worth using in a real-world app? -- it is disabled by default only in Debug configuration and Enabled in Release.
推荐答案
Scott Hanselman 有一篇博文 展示了/optimize(在 Release Builds 中启用)功能的几个示例.
Scott Hanselman has a blog post that shows a few examples of what /optimize (which is enabled in Release Builds) does.
作为一个总结:/optimize 做了很多没有给出确切数字或定义的事情，但其中一个更明显的是方法内联(如果你有一个方法 A()，它调用 B()，它调用 C()，它调用D()，编译器可能会跳过" B 和 C，直接从 A 转到 D)，这可能会导致 Release 构建中出现奇怪"的调用堆栈.
As a summary: /optimize does many things with no exact number or definition given, but one of the more visible are method inlining (If you have a Method A() which calls B() which calls C() which calls D(), the compiler may "skip" B and C and go from A to D directly), which may cause a "weird" callstack in the Release build.
这篇关于/optimize C# 编译器密钥的用途是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！