Examples of using 在编译 in Chinese and their translations into English
{-}
-
Political
-
Ecclesiastic
-
Programming
在编译时，形式base.
At compile-time, base-access expressions of the form base.第一个语句，声明，是在编译阶段被处理的。
在编译过程中添加与安全性相关的更多警告.
Adding more warnings related to security at compiling process.在编译来自coinmetrics.
After compiling data sourced from coinmetrics.在编译FreeBSD-STABLE之前，请仔细阅读/usr/src里的Makefile。
Before compiling FreeBSD-STABLE, read the Makefile in/usr/src carefully.例如，以下程序在编译时失败。
For example, the following program fails in compilation.其实Xcode在编译时会自动负责工作。
Actually the XCode takes care of the job automatically in compile time.在编译FreeBSD-CURRENT之前，请仔细阅读/usr/src里的Makefile文件。
Before compiling FreeBSD-CURRENT, read the Makefile in/usr/src carefully.静态类型的语言中，变量的类型是在编译时期确定的。
In some languages the variable type is defined at a translation stage.这些点在那里只是为了阻止在编译时的类型检查。
The dots aresimply there to prevent type checking during compilation.例如，以下Java程序在编译时失败。
For example, the following Java program fails in compilation.Rust不仅使得我们的API简单易用，也在编译时就消除了一整类的错误！!
Not only has Rust made our API easier to use,but it has also eliminated an entire class of errors at compile time!若要在编译时验证每个变量的类型，请将鼠标指针放在WriteLine语句中的dyn或obj上。
To verify the type of each variable at compile time, place the mouse pointer over dyn or obj in the WriteLine statements.不幸的是这个在编译时不可能，因为b的世纪类型可以随着程序运行而改变。
Unfortunately that isn't possible at compile-time because the actual type of the b variable can change as the program runs.这个例子显式的说明了，constexpr必须在编译中被判断为真，但是对于static_assert没有影响。
不幸的是，在某些系统上，Apache会在编译时检测sendfile的存在，即使它不能正常工作。
Unfortunately, on some systems,Apache will detect the presence of sendfile at compile-time, even when it does not work properly.Rust会在编译时抱怨我们尝试在要求不可反驳模式的地方使用可反驳模式：.
At compile time, Rust will complain that we have tried to use a refutable pattern where an irrefutable pattern is required:.Usr/obj包含了所有在编译阶段生成的目标文件。
Usr/obj contains all 语法错误，也被称为解析错误，在编译时进行传统的编程语言，并出现在JavaScript解释时。
Syntax errors, also called parsing errors, occur at compile time in traditional programming languages and TypeScript的类型系统允许某些在编译阶段无法确认其安全性的操作。
TypeScript's type system allowscertain operations that can't be known at compile-time to be safe.然而，类型化的中间语言更难以实现，因为在编译过程中把表示项的类型变得明确是必要的。
However, a typed intermediate language is more difficult to implement becausetypes that represent items made explicit during the compilation process are necessary.在这些情况下，转换仍存在，但在编译时将失败。
In these cases, a conversion still exists,but will fail at compile-time.在大多数语言中，在编译时知道一个变量有多大是非常重要的，如果我们想把它存储在堆栈中的话。
In most languages it's critical that we know at compile time how large a variable is if we want to store it on the stack.它也是类型安全的，在编译过程中可以捕获大部分错误。
It is also a type-safe and许多程序允许您在编译时指定某些选项，例如在构建时选择性地包括程序中的各种特征。
Many programs allow you to specify certain options at compile time, such as selectively including various features in the program when built.与C++中的constexpr不同，没有可以在编译时评估的constexpr函数或类型的概念，所以你不能这样做：.
Unlike constexpr in C++, there is no concept of constexpr functions ortypes that can be evaluated at compile time, so you can't do this:.这样，&str就有了一个在编译时可以知道的大小：它是usize长度的两倍。
As such,a&str has a size we can know at compile time: it's two times the size of a usize in length.此强类型保证在编译时捕获类型错误，以便可以在用户遇到这些错误之前更正它们。
This strong typingguarantees that type errors are caught at compile time when they can be corrected before users encounter them.该函数返回一个计算器，但系统在编译时不知道此计算器对象的精确类型。
The function returns a calculator, butthe system doesn't know the exact type of this calculator object at compile time.记住，Rust是静态类型（staticallytyped）语言，也就是说在编译时就必须知道所有变量的类型。
Keep in mind that Rust is a statically typed language,which means that it must know the types of all variables at compile time.
