Integrated: 8293839: Documentation memory consistency effects of runLater

[Jens Lidestrom]

On Wed, 17 Aug 2022 07:21:43 GMT, Jens Lidestrom <duke at openjdk.org> wrote:

> Prior to this change it was not clear from the documentation if callers of Platform#runLater must perform
> any synchronisation to have writes of the calling thread be visible in the JavaFX Application
> Thread. It is important to document either if callers can rely on runLater to do such synchronisation
> internally, or to document is users CAN NOT rely on runLater for this.
> 
> This change documents that actions in a thread prior to submitting a runnable to
> Platform#runLater happen-before actions performed by the runnable in the JavaFX
> Application Thread.
> 
> runLater inherits the memory consistency effects of InvokeLaterDispatcher in most cases. 
> InvokeLaterDispatcher uses BlockingDeque internally. This change documents this
> in the same way as it is documented by BlockingDeque.
> 
> Other implementations of runLater should have similar memory consistency effects.

This pull request has now been integrated.

Changeset: 7c6a54d4
Author:    Jens Lidestrom <jens at lidestrom.se>
Committer: Nir Lisker <nlisker at openjdk.org>
URL:       https://git.openjdk.org/jfx/commit/7c6a54d41945a21d2a4f0eceae56b5ba3df9f39f
Stats:     6 lines in 1 file changed: 6 ins; 0 del; 0 mod

8293839: Documentation memory consistency effects of runLater

Reviewed-by: kcr

-------------

PR: https://git.openjdk.org/jfx/pull/872