| commit | 5af984438298212fd821a091c013602b419340e5 | [log] [tgz] |
|---|---|---|
| author | Erik Ernst <eernst@google.com> | Mon Sep 17 11:39:24 2018 +0000 |
| committer | Erik Ernst <eernst@google.com> | Mon Sep 17 11:39:24 2018 +0000 |
| tree | 7db0c0d3d777f563f1ecb5dfd1d7d7b340c0ff55 | |
| parent | 2cb2ac401c130bc78ec104307f0cece420f73be5 [diff] |
Language specification reorganization. ---------------- NEW description (old description shown at end): This CL is now a reorganization, problem fixing, clarifying update to dartLangSpec.tex which was created as part of the work on the rules for call method extraction. That is, all the call method extraction specific elements have been _deleted_ from this CL (they will reappear as a separate CL later). This CL is now only performing "general clean-up work" which is needed in order to perform many kinds of updates (including call method extraction, but also anything else where the dynamic semantics depends on the static analysis & desugaring). ------------------------------------------------ OLD description Introduced rules for call method extraction. The previous update to dartLangSpec.tex dealt with invocations, but omitted the transformation whereby `e` becomes `e.call` when `e` has a type which is a class with a `call` method and the context expects a value of type `Function` or of a function type. This CL adds some rules dealing with that and introduces a concept for the transformation itself. One part is missing for the initial patch set: There are no rules specifying that call method extraction should be applied to actual arguments. The problem is that static checking of actual arguments to various invocations (function expression invocation, ordinary method invocation, super invocation, etc.etc.) seems to be "delegated" partially to section `Binding Actuals to Formals`, but that section never defines the syntax for the function which is being invoked and it is in general rather dynamic in nature. So I'm not quite sure that the references to static checking at the end of that section are located optimally. Some adjustments may therefor be needed before we can specify this particular feature for actual arguments. Change-Id: Ia2ab6f16cd50e10a3c467722035f0dc4adb50587 Reviewed-on: https://dart-review.googlesource.com/51323 Reviewed-by: Lasse R.H. Nielsen <lrn@google.com>
Dart is an open-source, scalable programming language, with robust libraries and runtimes, for building web, server, and mobile apps.
Visit the dartlang.org to learn more about the language, tools, getting started, and more.
Browse pub.dartlang.org for more packages and libraries contributed by the community and the Dart team.
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.