Commit 06a4958e authored by Omer Katz's avatar Omer Katz Committed by Commit Bot

Remove reference to EAGERLY_FINALIZE from Api reference

Bug: 981043
Change-Id: Ie5f2181a6503224579b45f03686c6cb6482d19e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1697625Reviewed-by: default avatarMichael Lippautz <mlippautz@chromium.org>
Commit-Queue: Omer Katz <omerkatz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#676353}
parent d9373636
...@@ -98,8 +98,7 @@ private: ...@@ -98,8 +98,7 @@ private:
Note that finalization is done at an arbitrary time after the object becomes unreachable. Note that finalization is done at an arbitrary time after the object becomes unreachable.
Any destructor executed within the finalization period must not touch any other on-heap object, because destructors Any destructor executed within the finalization period must not touch any other on-heap object, because destructors
can be executed in any order. If there is a need of having such destructor, consider using can be executed in any order.
[EAGERLY_FINALIZE](#EAGERLY_FINALIZE).
Because `GarbageCollectedFinalized<T>` is a special case of `GarbageCollected<T>`, all the restrictions that apply Because `GarbageCollectedFinalized<T>` is a special case of `GarbageCollected<T>`, all the restrictions that apply
to `GarbageCollected<T>` classes also apply to `GarbageCollectedFinalized<T>`. to `GarbageCollected<T>` classes also apply to `GarbageCollectedFinalized<T>`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment