angular-docs-cn/packages/compiler-cli/src/ngtsc/partial_evaluator/index.ts

/**
 * @license
 * Copyright Google Inc. All Rights Reserved.
 *
 * Use of this source code is governed by an MIT-style license that can be
 * found in the LICENSE file at https://angular.io/license
 */

export {DynamicValue} from './src/dynamic';
export {ForeignFunctionResolver, PartialEvaluator} from './src/interface';
export {BuiltinFn, EnumValue, ResolvedValue, ResolvedValueArray, ResolvedValueMap} from './src/result';
refactor(ivy): split apart the 'metadata' package in the ngtsc compiler (#27743) This refactoring moves code around between a few of the ngtsc subpackages, with the goal of having a more logical package structure. Additional interfaces are also introduced where they make sense. The 'metadata' package formerly contained both the partial evaluator, the TypeScriptReflectionHost as well as some other reflection functions, and the Reference interface and various implementations. This package was split into 3 parts. The partial evaluator now has its own package 'partial_evaluator', and exists behind an interface PartialEvaluator instead of a top-level function. In the future this will be useful for reducing churn as the partial evaluator becomes more complicated. The TypeScriptReflectionHost and other miscellaneous functions have moved into a new 'reflection' package. The former 'host' package which contained the ReflectionHost interface and associated types was also merged into this new 'reflection' package. Finally, the Reference APIs were moved to the 'imports' package, which will consolidate all import-related logic in ngtsc. PR Close #27743 2018-12-18 09:48:15 -08:00			`/**`
			`* @license`
			`* Copyright Google Inc. All Rights Reserved.`
			`*`
			`* Use of this source code is governed by an MIT-style license that can be`
			`* found in the LICENSE file at https://angular.io/license`
			`*/`

feat(ivy): DynamicValue now indicates why the value is dynamic (#27697) This commit changes the partial evaluation mechanism to propagate DynamicValue errors internally during evaluation, and not to "poison" entire data structures when a single value is dynamic. For example, previously if any entry in an array was dynamic, evaluating the entire array would return DynamicValue. Now, the array is returned with only the specific dynamic entry as DynamicValue. Instances of DynamicValue also report the node that was determined to be dynamic, as well as a potential reason for the dynamic-ness. These can be nested, so an expression `a + b` may have a DynamicValue that indicates the 'a' term was DynamicValue, which will itself contain a reason for the dynamic-ness. This work was undertaken for the implementation of listLazyRoutes(), which needs to partially evaluate provider arrays, parts of which are dynamic and parts of which contain useful information. PR Close #27697 2018-11-15 13:58:43 +01:00			`export {DynamicValue} from './src/dynamic';`
refactor(ivy): split apart the 'metadata' package in the ngtsc compiler (#27743) This refactoring moves code around between a few of the ngtsc subpackages, with the goal of having a more logical package structure. Additional interfaces are also introduced where they make sense. The 'metadata' package formerly contained both the partial evaluator, the TypeScriptReflectionHost as well as some other reflection functions, and the Reference interface and various implementations. This package was split into 3 parts. The partial evaluator now has its own package 'partial_evaluator', and exists behind an interface PartialEvaluator instead of a top-level function. In the future this will be useful for reducing churn as the partial evaluator becomes more complicated. The TypeScriptReflectionHost and other miscellaneous functions have moved into a new 'reflection' package. The former 'host' package which contained the ReflectionHost interface and associated types was also merged into this new 'reflection' package. Finally, the Reference APIs were moved to the 'imports' package, which will consolidate all import-related logic in ngtsc. PR Close #27743 2018-12-18 09:48:15 -08:00			`export {ForeignFunctionResolver, PartialEvaluator} from './src/interface';`
feat(ivy): DynamicValue now indicates why the value is dynamic (#27697) This commit changes the partial evaluation mechanism to propagate DynamicValue errors internally during evaluation, and not to "poison" entire data structures when a single value is dynamic. For example, previously if any entry in an array was dynamic, evaluating the entire array would return DynamicValue. Now, the array is returned with only the specific dynamic entry as DynamicValue. Instances of DynamicValue also report the node that was determined to be dynamic, as well as a potential reason for the dynamic-ness. These can be nested, so an expression `a + b` may have a DynamicValue that indicates the 'a' term was DynamicValue, which will itself contain a reason for the dynamic-ness. This work was undertaken for the implementation of listLazyRoutes(), which needs to partially evaluate provider arrays, parts of which are dynamic and parts of which contain useful information. PR Close #27697 2018-11-15 13:58:43 +01:00			`export {BuiltinFn, EnumValue, ResolvedValue, ResolvedValueArray, ResolvedValueMap} from './src/result';`