Skip to content
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

Finished draft translations. #1

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

europa-east
Copy link

The following 2 docs were finished translations.

  1. interacting-with-julia.rst
  2. embedding.rst
    So, please review them and feedback.
    Thank you very much.

@@ -171,7 +265,12 @@ The garbage collector also operates under the assumption that it is aware of eve

It is in general impossible to predict which values will be old at runtime, so the write barrier must be inserted after all explicit stores. One notable exception is if the ``parent`` object was just allocated and garbage collection was not run since then. Remember that most ``jl_...`` functions can sometimes invoke garbage collection.

The write barrier is also necessary for arrays of pointers when updating their data directly. For example::
どのオブジェクト(値)が、実行時に旧世代になるかを予測することは可能です。書き込み防止は、明示的に全てのオブジェクトがメモリ上に保持された後に設定されます。一つの例外は、 ``parent`` オブジェクトのメモリがちょうど確保された後に、ガベージコレクションが動作しないときです。
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

「... 予測することは不可能です」でしょうか。

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

原文「Remember that most jl_... functions can sometimes invoke garbage collection.」に対応する訳文がないように思えますが、どうでしょうか。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants