当然，还会失去编译时检查的安全保障。
Of course, you also give up the safety net of the compile-time type checking.
大部份安全策略设置只在模板被编译时检查。
Must security policy Settings are only checked when the template gets compiled.
这是一个编译时检查。
元数据更重要的优点是编译器可以使用它来执行基本的编译时检查。
A more significant advantage of metadata is the ability for a compiler to use it to perform some basic compile-time checking.
元数据可以用于创建文档，跟踪代码中的依赖性，甚至执行基本编译时检查。
Metadata can be used to create documentation, to track down dependencies in code, and even to perform rudimentary compile-time checking.
基于注释属性的切入点有某些好处，特别是对于编译时检查和静态选择的效率。
There are certain advantages to annotation properties-based pointcuts, especially for compile-time checks and efficiency of static selection.
SIGNAL和SLOT宏将他们的观点转化为字符串，他们不是在编译时检查(因为…他们实际上是字符串)。
SIGNAL and SLOT macros turn their arguments into strings, and they are not checked in compile time (because... they are string actually).
这条XML消息将进行编译时检查，以确保语法正确和格式良好，并获得一些标准servlet（或JSP）不具备的好处。
The XML message will be compile-time checked to make sure that it is syntactically correct and well-formed, something we don't get with standard servlets (or JSP, for that matter).
mwarn-framesize=framesize和 -mwarn-dynamicstack：这些选项会引起在编译时检查函数是否超过给定的堆栈帧（stack frame）大小或使用动态调整的堆栈帧。
mwarn-framesize=framesize and -mwarn-dynamicstack: These options cause a compile-time check whether a function exceeds a given stack frame size or uses dynamically sized stack frames.
SQLJ可以通过在编译时使用数据库连接，对代码执行语法和语义上的检查。
SQLJ can perform syntactic and semantic checking on the code, using database connections at compile time.
该编译过程牵涉到授权检查、优化，以及将语句转化为可执行格式时所需的其他一些活动。
This compilation process involves authorization checking, optimization, and other activities necessary to convert the statement into an executable form.
虽然付出了这一点成本，但可以得到非常好的性能，编译时类型检查，以及一个非常高级的语言。
For the trouble, you get rock-solid performance, compile-time type checking, and a very high-level language.
Scala甚至使得把null作为第二个参数传给构造函数变得很困难；它不会再编译时做类型检查。
Scala even makes it difficult to pass null as the second parameter to the constructor; it won't type check when you compile it.
它不会再编译时做类型检查。
因为您配置现实世界的对象时，会得到一些编译时错误检查。
Because you're configuring real-world objects, you get some compile time error checking.
查询编译器在检查字符比较操作时使用该信息，以决定如何执行操作。
The query compiler uses this information while checking any character comparison operations, to decide how to evaluate the operations.
一定要记住，在使用静态断言时，检查的表达式在编译时必须是可计算的。
While using static assertions, always remember that the expression being checked must be evaluable at compile time.
编译器会根据契约来检查代码是否满足了所有的条件，并在出现状况时发出警告。
The compiler will make specific checks via Contracts to ensure that all the conditions specified are met, issuing warning if they are not.
Go所带来的一个最强大的特性之一就是提供了可以在编程时运用动态类型的思想而把行为定义的合法性检查的工作推到编译时。
One of the most powerful features that Go brings with it is the ability to program with that duck-typed mentality, and check for adherence to those defined behaviors at compile time.
同样，对“外露”类型参数的instance of检查将在编译时产生“unchecked”警告，而且检查将不会如期在运行时进行。
Similarly, instanceof checks on naked type parameters will result in an "unchecked" warning at compile time and the check will not occur as expected at runtime.
大部分时候，这些检查并不会实际做什么事情，实际上，有时它们只是为现有bug创造一些令人兴奋的新机会，举例来说，在交叉编译时就需要如此。
Most of the time, these checks really don't do anything, and indeed, sometimes they just create exciting new opportunities for bugs, for instance when cross-compiling.
如果一个非容器控件（比如TextBox）被放置在form标记之外，将会抛出一个运行时错误（编译时不会对此进行检查）。
If a non-container control (TextBox, for example) is placed outside the form tag, an HttpException is thrown at run time (no check is made for this at compile time).
当编写表达式时，编译器检查表达式中的对象是否按该对象的类型定义的使用方式使用。
When we write an expression, the compiler checks that the objects used in the expression are used in ways that are defined by the type of the objects.
缺点是，第二个版本是难以阅读，而不是保护的编译时的语法和语义检查。
The downside is that the second version is harder to read, and is not protected by compile-time syntax and semantic checking.
我希望检查后，编译器会警告我时，我使用一个库，不包括客户的子网。
I hoped that after checking this, the compiler would warn me when I use a library that is not included in client subset of. NET.
GCC的一个缺陷是，它并没有接近尽可能多的调试检查微软的编译器编译时没有优化。
One of GCC's flaws is that it doesn't do anywhere near as much debug checking as Microsoft's compiler when compiling without optimizations.
汇入中继资料时，编译器会在编译时期检查这项资讯。
Compilers inspect this information, at compile time, when importing metadata.
泛型相当有用，因为他们提供强制的编译时类型检查，要求更少的数据类型之间的显式转换，并减少装箱拆箱的操作和运行时类型检查。
Generics are useful because they provide stronger compile-time type checking, require fewer explicit conversions between data types, and reduce the need for boxing operations and run-time type checks.
链接需求：对调用方进行JIT编译时，会检查直接调用方的权限。
Link Demands for the permission: the permissions of the immediate caller are checked when the caller is JIT-compiled.
当检查类型定义时，编译器需要知道哪个集合包含类型定义信息，以便把它加到结果文件里。
When checking for a type '; s definition, the compiler must know which assembly contains the type so that the assembly information and the type information can be emitted into the resulting file.
应用推荐