isolates in frog: playing with API improvements

corelib/src/isolate.dart

 // Copyright (c) 2011, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 // Dart core library.
+// TODO(sigmund): move to dart:isolate
 
 /**
  * [SendPort]s are created from [ReceivePort]s. Any message sent through
  * a [SendPort] is delivered to its respective [ReceivePort]. There might be
  * many [SendPort]s for the same [ReceivePort].
  *
  * [SendPort]s can be transmitted to other isolates.
  */
 interface SendPort extends Hashable {
 
@@ skipping 87 matching lines @@
  * and invokes the instance method [main].
  *
  * The new instance is created by invoking the default constructor of the
  * class that served as template for spawning the new isolate. This means, that
  * sub-classes must have a default constructor (i.e. no-argument constructor).
  *
  * Isolates may be "heavy" or "light". Heavy isolates live in their own thread,
  * whereas "light" isolates live in the same thread as the isolate which spawned
  * them.
  */
+// TODO(sigmund): delete once we implement the new isolates in the vm
 class Isolate {
 
   /**
    * Redirects to [Isolate.light].
    */
   Isolate() : this.light();
 
   /**
    * Creates a new isolate-template for a light isolate.
    */
@@ skipping 48 matching lines @@
   /**
    * When isolates are created, an instance of the template's class is
    * instantiated in the new isolate. After the [port] has been set up, this
    * [main] method is invoked on the instance.
    */
   abstract void main();
 
   final bool _isLight;
   ReceivePort _port;
 }