<commit_before>// Copyright (c) 2012, 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.


/**
 * The `dart:isolate` library defines APIs to spawn and communicate with
 * isolates.
 *
 * All code in dart runs in the context of an isolate. Each isolate has its own
 * heap, which means that all values in memory, including globals, are available
 * only to that isolate. The only mechanism available to communicate between
 * isolates is to pass messages. Messages are sent through ports. This library
 * defines [ReceivePort] to represent the receiver's end of a communication
 * channel, and [SendPort] to represent the sender's end.
 *
 * All isolates start with an initial receive port, which is set in the
 * top-level property [port]. This port is used to establish the first
 * communication between isolates.
 *
 * Two APIs are available to spawn a new isolate: [spawnFunction] and
 * [spawnUri]. [spawnFunction] creates a new isolate that is using the same
 * source code as the current isolate, [spawnUri] allows spawning an isolate
 * that was written independently.
 *
 * There is currently no way to indicate in the API whether the isolates should
 * run on the same or different threads. The underlying system will schedule the
 * isolate were appropriate. In the near future we will add an API to create DOM
 * isolates. These are isolates that share access to the DOM. All DOM isolates
 * will run on the UI thread.
 *
 * This library is still evolving. New APIs are being added, and some will be
 * deprecated and removed. In particular, the class [Isolate] will be
 * deprecated as soon the dartvm has an implementation working for
 * [spawnFunction] and [spawnUri], and we have an API to spawn DOM isolates.
 */
#library("dart:isolate");

//#import("../uri/uri.dart");
#import("../../frog/leg/lib/uri_toremove.dart");
#source("isolate_api.dart");
#source("frog/compiler_hooks.dart");
#source("frog/isolateimpl.dart");
#source("frog/ports.dart");
#source("frog/messages.dart");<commit_msg>Remove the leg-specific uri file, originally added because we did not handle compike-time constants fully. Review URL: https://chromiumcodereview.appspot.com//9700095<commit_after>// Copyright (c) 2012, 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.


/**
 * The `dart:isolate` library defines APIs to spawn and communicate with
 * isolates.
 *
 * All code in dart runs in the context of an isolate. Each isolate has its own
 * heap, which means that all values in memory, including globals, are available
 * only to that isolate. The only mechanism available to communicate between
 * isolates is to pass messages. Messages are sent through ports. This library
 * defines [ReceivePort] to represent the receiver's end of a communication
 * channel, and [SendPort] to represent the sender's end.
 *
 * All isolates start with an initial receive port, which is set in the
 * top-level property [port]. This port is used to establish the first
 * communication between isolates.
 *
 * Two APIs are available to spawn a new isolate: [spawnFunction] and
 * [spawnUri]. [spawnFunction] creates a new isolate that is using the same
 * source code as the current isolate, [spawnUri] allows spawning an isolate
 * that was written independently.
 *
 * There is currently no way to indicate in the API whether the isolates should
 * run on the same or different threads. The underlying system will schedule the
 * isolate were appropriate. In the near future we will add an API to create DOM
 * isolates. These are isolates that share access to the DOM. All DOM isolates
 * will run on the UI thread.
 *
 * This library is still evolving. New APIs are being added, and some will be
 * deprecated and removed. In particular, the class [Isolate] will be
 * deprecated as soon the dartvm has an implementation working for
 * [spawnFunction] and [spawnUri], and we have an API to spawn DOM isolates.
 */
#library("dart:isolate");

#import("dart:uri");
#source("isolate_api.dart");
#source("frog/compiler_hooks.dart");
#source("frog/isolateimpl.dart");
#source("frog/ports.dart");
#source("frog/messages.dart");
{'fraction_non_alphanumeric': 0.07970849464814393, 'fraction_numerical': 0.003416078342063311, 'mean_word_length': 4.173144876325089, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7221060', 'n_tokens_mistral': 1203, 'n_tokens_neox': 1130, 'n_words': 607}