2d1c691625
Now that null contexts are impossible during analyzer resolution (https://dart-review.googlesource.com/c/sdk/+/357522), it's possible to make a lot of variables, fields and parameters that represent contexts non-nullable. This change propagates non-nullability of contexts through the analyzer to the extent that can be done reasonably quickly and safely. In particular, it makes the following changes: - It changes the following helper methods so that they no longer accept a `null` context: - TypeSystemImpl.acceptsFunctionType - TypeSystemImpl.refineNumericInvocationContext - TypeSystemImpl.setupGenericTypeInference - TypeSystemImpl._refineNumericInvocationContextNullSafe - InvocationInferenceHelper.inferTearOff - InvocationInferenceHelper.resolveMethodInvocation - ElementResolver.visitMethodInvocation - ErrorDetectionHelpers.getImplicitCallMethod - ResolverVisitor.insertGenericFunctionInstantiation - ResolverVisitor._insertImplicitCallReference - ResolverVisitor._resolveRewrittenFunctionExpressionInvocation - StaticTypeAnalyzer.visitConditionalExpression - StaticTypeAnalyzer.visitIntegerLiteral - AstResolver.resolveExpression - It changes the following classes so that their `resolve` methods no longer accept a `null` context (nor do the methods that those `resolve` methods defer to): - AssignmentExpressionResolver - BinaryExpressionResolver - ConstructorReferenceResolver - FunctionExpressionInvocationResolver - FunctionExpressionResolver - InstanceCreationExpressionResolver - MethodInvocationResolver - PostfixExpressionResolver - PrefixExpressionResolver - PrefixedIdentifierResolver - RecordLiteralResolver - SimpleIdentifierResolver - TypedLiteralResolver - It changes all the classes in the `InvocationInferrer` class hierarchy so that they no longer accept a `null` context. - It changes the following helper methods so that they no longer return a `null` context: - AssignmentExpressionResolver._computeRhsContext - InvocationInferrer._computeContextForArgument - MethodInvocationInferrer._computeContextForArgument - YieldStatementResolver._computeContextType - It changes PropertyElementResolverResult.indexContextType so that it no longer can be `null`. - It ensures that the analyzer always passes a non-null context to the _fe_analyzer_shared method `TypeAnalyzer.analyzeExpression`. This will pave the way for a follow-up CL that makes that method stop accepting `null`. In many cases, to accomplish this, it was necessary to make explicit use of the unknown type schema `_` (UnknownInferredType.instance). Although adding these explicit uses makes the code a bit more verbose, it's not really fundamentally more complex than it was before; previously, the code used `null` to represent `_` in these cases (sometimes implicitly). Change-Id: I1479e7c59969c59ea67abef30daa6a516b15ed97 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358662 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> |
||
|---|---|---|
| .dart_tool | ||
| .github | ||
| benchmarks | ||
| build | ||
| docs | ||
| pkg | ||
| runtime | ||
| samples | ||
| sdk | ||
| tests | ||
| third_party | ||
| tools | ||
| utils | ||
| .clang-format | ||
| .gitattributes | ||
| .gitconfig | ||
| .gitignore | ||
| .gn | ||
| .mailmap | ||
| .style.yapf | ||
| AUTHORS | ||
| BUILD.gn | ||
| CHANGELOG.md | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| DEPS | ||
| LICENSE | ||
| OWNERS | ||
| PATENT_GRANT | ||
| PRESUBMIT.py | ||
| README.dart-sdk | ||
| README.md | ||
| sdk.code-workspace | ||
| sdk_args.gni | ||
| SECURITY.md | ||
| WATCHLISTS | ||
Dart
An approachable, portable, and productive language for high-quality apps on any platform
Dart is:
-
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
-
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
-
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
-
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
-
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
Building Dart
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.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.