Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 // Copyright (c) 2016, the Dart project authors. Please see the AUTHORS file | |
| 2 // for details. All rights reserved. Use of this source code is governed by a | |
| 3 // BSD-style license that can be found in the LICENSE file. | |
| 4 | |
| 5 /// Defines the front-end API for converting source code to summaries. | |
| 6 library front_end.summary_generator; | |
| 7 | |
| 8 import 'dart:async'; | |
| 9 import 'options.dart'; | |
| 10 | |
| 11 /// Creates a summary representation of the build unit whose source files are in | |
| 12 /// [sources]. | |
| 13 /// | |
| 14 /// Intended to be a part of a modular compilation process. | |
| 15 /// | |
| 16 /// [sources] should be the complete set of source files for a build unit | |
| 17 /// (including both library and part files). | |
| 18 /// | |
| 19 /// The summarization process is hermetic, meaning that the only files which | |
| 20 /// will be read are those listed in [sources], [Options.inputSummaries], and | |
| 21 /// [Options.sdkSummary]. If a source file attempts to refer to a file which is | |
| 22 /// not obtainable from these paths, that will result in an error, even if the | |
| 23 /// file exists on the filesystem. | |
| 24 /// | |
| 25 /// Any `part` declarations found in [sources] must refer to part files which | |
| 26 /// are also listed in [sources], otherwise an error results. (It is not | |
| 27 /// permitted to refer to a part file declared in another build unit). | |
| 28 /// | |
| 29 /// The return value is a list of bytes to write to the summary file. | |
|
Siggi Cherem (dart-lang)
2016/10/17 16:27:29
Not sure yet about the use cases, but are there si
Paul Berry
2016/10/17 17:04:27
At the moment I can't imagine a scenario where it
| |
| 30 Future<List<int>> summarizeBuildUnit(Options options, List<Uri> sources) => | |
| 31 throw new UnimplementedError(); | |
| OLD | NEW |