The end result is much less XML and much more type safety.
最终的结果就是更少的XML但更多的类型安全性。
Sitebricks does not compromise type safety or performance.
Sitebricks不会破坏类型安全或性能。
To increase type safety, this could also be an enumeration.
为了提高类型安全性,这也可以是一个枚举。
Q: What sorts of type safety do you think are needed for XSLT?
问:您认为XSLT需要什么样的类型安全?
The usual benefits of type safety as enabled by service contracts.
常见的类型安全好处都是通过服务协约实现的。
The language supports type safety and makes code maintenance easier.
这种语言支持类型安全性,使代码维护更轻松。
We both shared a dislike of macros and a liking for type safety.
我们都讨厌宏而喜欢类型安全。
Simply put, generics provide compile-time type safety for collections.
简单来说,泛型为集合提供了编译时类型安全。
A variable may be bound to a specific data type to help provide type safety.
变量可以绑定到特定的数据类型来确保类型安全。
These days, compiler will take care of type safety and will track type information.
如今,编译器会检查类型安全性,跟踪类型信息。
Generics provide type safety without the overhead of multiple implementations.
泛型提供了类型安全但没有增加多个实现的开销。
The developer would need to ensure type safety and handle high-level types manually.
开发人员需要确保类型安全,并且需要手动处理高级类型。
We recommend that you define a generic class when you want to ensure type safety.
我们建议在需要确保类型安全时定义泛型类。
The other verification that we rely on (C# type safety and channel contracts) have been very useful.
另一个我们所依赖的验证(C#类型安全和通道契约)也是非常有用的。
However, because of generics, the compiler now throws warnings when collections are used without type safety.
然而,因为泛型,当使用集合而没有类型安全时,编译器将抛出警告。
Each business rule group supports the operation signatures defined in a provided interface, thus enabling type safety.
每个业务规则组均支持在提供的接口中定义的操作,从而实现了类型安全。
Furthermore, due to a novel approach to bytecode verification, we're also able to ensure runtime type safety of the compiled code.
此外,由于采用了新的方式对字节码进行校验,我们还能确保编译的代码在运行时的类型安全。
While Verve is written in C# for convenient automatic compilation to TAL, a second check is still performed to verify type safety.
尽管为了便于自动编译成TAL,Verve是由C#编写的,但它还是执行了二次检查来验证类型安全性。
Essentially, type safety means that a program cannot perform an operation on an object unless that operation is valid for that object.
本质上,类型安全性意味着,除非程序的操作对于类型是合法的,否则就无法在对象上执行操作。
Rails is surprisingly dynamic and, therefore, was built on a programming language (Ruby) that does not require rigid constructs and type safety.
Rails的动态性让我们惊叹,它是在不需要严格的构造和类型安全性的编程语言(Ruby)的基础上构建的。
You can then treat each named value as an instance of that class, providing you with compile-time type safety that a named set of integers can't.
然后,可以将每个指定的值看作是那个类的一个实例,这为您提供了指定的整数集合所无法提供的编译时类型安全。
The type safety allowed compile-time resolution of some things that C-style libraries resolve at run-time, thus giving excellent performance.
类型安全允许一些原本在C风格库中需要在运行时决定的事,可在编译时决定,因而提供了非凡的性能。
That contract does not allow this method to throw a run-time exception (barring violations of generic type safety that qualify as bugs in the calling code).
这个合约不允许该方法抛出运行时异常(防止因违反泛型类型安全而成为调用代码中的bug)。
According to customer requirements, the upturning type safety protective cover is adopted, which is featured by simple operation and beautiful appearance.
可根据客户要求,采用上翻式安全防护罩,操作简便,外形美观。
Although verification of type safety is not mandatory to run managed code, type safety plays a crucial role in assembly isolation and security enforcement.
尽管类型安全验证对于运行托管代码不是强制的,但类型安全在程序集隔离和安全性强制中起着至关重要的作用。
By allowing you to specify types that are acted on by a generic class or method, the generics feature shifts the burden of type safety from you to the compiler.
通过允许指定泛型类或方法操作的类型,泛型功能将类型安全的任务从您转移给了编译器。
This means that all program elements have a definite type at compile time, guaranteeing type safety, but that you do not have to specify the types of every value explicitly.
这意味着,所有程序元素的类型在编译时都要明确,从而确保类型安全,但您不需要显式指定每个值的类型。
i.e.: A question to be answered: will the developers prefer to use Hibernate-style Criteria throug Strings, or will they use the newly created StaticMetaModel approach for type safety?
也就是必须要回答一个问题:开发者们会喜欢通过String来使用Hibernate风格的Criteria,还是愿意使用新创建的 StaticMetaModel方式来保证类型安全?
Some say they simplify programming by extending the reach of the type system and therefore the compiler's ability to verify type safety; others say that they add more complexity than they're worth.
一部分人认为泛型简化了编程,扩展了类型系统从而使编译器能够检验类型安全;另外一些人认为泛型添加了很多不必要的复杂性。
On the downside, multiple interfaces incur a loss of static type safety because interfaces are selected only at runtime, which makes the system more vulnerable to latent bugs that can escape testing.
多接口的缺点是,它招致了静态类型安全性的损失,因为接口只在运行时被选择,这使得系统更容易受到潜伏错误的伤害,即那些逃过测试的错误。
应用推荐