Skip to content

thread safety... FIXED! #296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 8, 2014
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ja/overviews/reflection/thread-safety.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ title: スレッドセーフティ
残念ながら Scala 2.10.0 でリリースされた現行の状態ではリフレクションはスレッドセーフではない。
[SI-6240](https://issues.scala-lang.org/browse/SI-6240) が報告されているので、それを使って進捗を追跡したり、技術的な詳細を照会することができるが、ここに現状で分かっていることをまとめてみたい。

<span class="label success">NEW</span> Thread safety issues have been fixed in Scala 2.11.0-RC1, but we are going to keep this document available for now, since the problem still remains in the Scala 2.10.x series, and we currently don't have concrete plans on when the fix is going to be backported.

現在の所、リフレクション関連では 2通りの競合状態があることが分かっている。第一はリフレクションの初期化
(`scala.reflect.runtime.universe` が最初にアクセルされるときに呼ばれるコード)
は複数のスレッドから安全に呼び出すことができない。
Expand Down
2 changes: 2 additions & 0 deletions overviews/reflection/thread-safety.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ Unfortunately, in its current state released in Scala 2.10.0, reflection is not
There's a JIRA issue [SI-6240](https://issues.scala-lang.org/browse/SI-6240), which can be used to track our progress
and to look up technical details, and here's a concise summary of the state of the art.

<span class="label success">NEW</span> Thread safety issues have been fixed in Scala 2.11.0-RC1, but we are going to keep this document available for now, since the problem still remains in the Scala 2.10.x series, and we currently don't have concrete plans on when the fix is going to be backported.

Currently we know about two kinds of races associated with reflection. First of all, reflection initialization (the code that is called
when `scala.reflect.runtime.universe` is accessed for the first time) cannot be safely called from multiple threads. Secondly, symbol
initialization (the code that is called when symbol's flags or type signature are accessed for the first time) isn't safe as well.
Expand Down