[dart-misc] [dart-announce] BREAKING CHANGE: Isolate.pause, Isolate.kill in v1.11

['Lasse R.H. Nielsen' via Dart Announcements]

The Isolate methods are now implemented in both dart2js and the VM, so we
in version 1.11 we will remove the "experimental" marker.
As a result of implementing the features on the VM it became apparent that
the "Isolate.AS_EVENT" priority doesn't actually work as we wanted it to
because there is no guaranteed ordering between messages sent on different
send-ports. An "AS_EVENT" ping sent on the isolate control port may arrive
before an earlier data event sent on another send-port. We removed the
"AS_EVENT" priority since it didn't actually guarantee anything.

We also added an optional `response` parameter to the `ping` method so the
same receiver can be used to receive multiple pings and distinguish between
them. That meant that the existing optional `pingType` parameter was
changed to a named parameter, and for consistency, both `ping` and `kill`
now takes their priority priority parameter as a named parameter named
`priority`.

Fix: Existing code that used the optional priority/pingType parameter for
ping or kill must prefix the argument by "priority:". If they use
Isolate.AS_EVENT, they can change it to Isolate.BEFORE_NEXT_EVENT, or if
they tried to use it to know when a message is delivered on a different
port, they may need to change the communication protocol to get that
information in a different way - since it never actually worked.

Cheers!
/L
--
Lasse R.H. Nielsen - ***@google.com
'Faith without judgement merely degrades the spirit divine'
Google Denmark ApS - Frederiksborggade 20B, 1 sal - 1360 KÞbenhavn K
- Denmark - CVR nr. 28 86 69 84
--
For more news and information, visit https://plus.google.com/+dartlang

To join the conversation, visit https://groups.google.com/a/dartlang.org/