thread safety 中文意思是什麼
thread safety
解釋
線程安全性-
" february 2003, which discusses thread - safety benefits of immutability
」 （ 2003年2月） ，它討論了不變性對于線程安全的好處。 -
" february 2003, which discussed thread - safety benefits of immutability
」 （ 2003年2月） ，討論了線程安全在不變性方面的優點。 -
Thread safety relates to the fact that clients using a notifier in a multithreaded environment should not have to be concerned with thread synchronization issues ? subscribers will need to, but the notifier should not
線程安全也就是要使客戶程序在多線程環境中使用此通知機制的時候不需要關心線程同步的問題事件關注者需要，而事件通知者不需要。 -
Do not rely on finalization to provide thread safety
不要依賴終止來提供線程安全。 -
This idiom derives its thread safety from the fact that operations that are part of class initialization, such as static initializers, are guaranteed to be visible to all threads that use that class, and its lazy initialization from the fact that the inner class is not loaded until some thread references one of its fields or methods
這個idiom由屬于類初始化的操作（如靜態初始化器）保證對使用這個類的所有線程都是可見的這一事實衍生其線程安全性，內部類直到有線程引用其欄位或者方法時才裝載這一事實衍生出遲緩初始化。 -
The inconsistent synchronization detector is probably the most complicated detector used by findbugs ; it has to analyze the whole program, not just individual methods, use dataflow analysis to determine when a lock is held, and use heuristics to infer that a class intends to provide thread - safety guarantees
Inconsistent synchronization檢測器很可能是findbugs所使用的最復雜的檢測器；它必須分析整個程序，而不僅僅是單個方法，使用數據流分析來確定什麼時候加鎖，並使用直觀推斷來推出一個類想要提供線程安全保證。 -
Don t confuse reentrance with thread - safety
不要混淆可重入與線程安全。 -
Thread safety is not an all - or - nothing proposition
線程安全不是一個非真即假的命題 -
Object for the duration of the iteration. as the above example shows, thread safety is not all - or - nothing. the methods of
如上面的例子所示，線程安全性不是一個非真即假的命題。 -
Unfortunately, thread safety is not an all - or - nothing proposition, and it is surprisingly difficult to define
不幸的是，線程安全並不是一個非真即假的命題，它的定義出人意料的困難。 -
Has been audited for thread - safety under both the old and new memory models
中的版本在老的和新的內存模型中都已通過線程安全審核。 -
It is easy to " forget " this rule, especially when reading - but doing so creates numerous risks for the thread - safety of your program
很容易「忘記」這個規則，特別是在讀取時但是這么做可以造成很多有關程序線程安全的風險。 -
No table - wide locking is needed or even possible to provide thread - safety when iterating the collection
在對集合進行迭代時，不需要表范圍的鎖就能提供線程安全性。 -
Because there is no declarative way of describing a class s thread - safety behavior, it must be described textually
因為（還）沒有描述類的線程安全行為的聲明式方式，所以必須用文字描述。 -
A class s thread - safety behavior is an intrinsic part of its specification, and should be part of its documentation
一個類的線程安全行為是其規格說明中的固有部分，應該成為其文檔的一部分。 -
No widely accepted set of terms is available for the various levels of thread safety that commonly occur in java classes, but it is important that you make some attempt to document the thread - safety behavior of your classes while they are being written
對于java類中常見的線程安全性級別，沒有一種分類系統可被廣泛接受，不過重要的是在編寫類時盡量記錄下它們的線程安全行為。 -
But there are limitations to its thread safety, namely that there are state dependencies between certain pairs of methods
但是它的線程安全性是有限制的，即在某些方法之間有狀態依賴（類似地，如果在迭代過程中 -
Which appeared as part of the collections framework in jdk 1. 2, addressed thread - safety by providing an unsynchronized base class and a synchronized wrapper,
是作為jdk1 . 2中的集合框架的一部分出現的，它通過提供一個不同步的基類和一個同步的包裝器 -
Because the reference counting algorithm implicitly serializes operations, a certain amount of thread safety is also lost
由於引用計數演算法對操作進行隱式序列化，因此也會損失一定的線程安全性。 -
Contains a mutable reference to an immutable array, so as long as that reference is held fixed, you get all the thread - safety benefits of immutability without the need for locking
含有對一個不可變數組的一個可變的引用，因此，只要保留好那個引用，您就可以獲得不可變的線程安全性的好處，而且不用鎖定列表。
分享友人