Lines Matching refs:lazy

7 > - The lazy import is supported since API version 12.
9 > - To use the lazy import syntax on API version 12, you need to configure **"compatibleSdkVersionS…
14 With the lazy import, unnecessary files are not loaded in the cold start phase until these files ar…
18 …lazy** identifier for the invoking points of these files. Notice that subsequent synchronous loadi…
22 > You are not advised to blindly add **lazy** identifiers, which also increases the identification …
26 - Use lazy import.
30         import lazy { a } from "./mod1";    // "mod1" is not executed.
57 - Reference lazy import and native import for the same module at the same time.
61         import lazy { a } from "./mod1";    // "mod1" is not executed.
94     If the keyword **lazy** is deleted from **main.ets** file, the execution sequence is as follows:
109 | import lazy { x } from "mod";        | "mod"         | "x"         | "x"         | Yes           …
110 | import lazy { x as v } from "mod";   | "mod"         | "x"         | "v"         | Yes.          …
112 - The shared module is lazy imported or the dependency path contains the shared module.
120     export lazy var v;                  // The compiler reports an application compilation error.
121     export lazy default function f(){}; // The compiler reports an application compilation error.
122     export lazy default function(){};   // The compiler reports an application compilation error.
123     export lazy default 42;             // The compiler reports an application compilation error.
124     export lazy { x };                    // The compiler reports an application compilation error.
125     export lazy { x as v };               // The compiler reports an application compilation error.
126     export lazy { x } from "mod";         // The compiler reports an application compilation error.
127     export lazy { x as v } from "mod";    // The compiler reports an application compilation error.
128     export lazy * from "mod";           // The compiler reports an application compilation error.
130     import lazy v from "mod";           // The compiler reports an application compilation error.
131     import lazy * as ns from "mod";     // The compiler reports an application compilation error.
138 …import lazy type { obj } from "./mod";    // Not supported. The compiler reports an application co…
139 …import type lazy { obj } from "./mod";    // Not supported. The compiler reports an application co…
145 - In the same ets file, not all the dependency modules that require the lazy import are added lazy …
147 …Incomplete labeling will cause lazy loading to fail and increase the overhead of identifying lazy …
150 …  import lazy { a } from "./mod1";    // Obtain the object a from "mod1" and add a lazy identifier.
152 …";         // Obtain the attributes in "mod1". This syntax is not added a lazy identifier, so "mod…
156 - In the same ETS file, lazy loading variables are not used and exported again. Lazy loading variab…
165 …  import lazy { a } from "./mod1";    // Obtain the object a from "mod1" and add a lazy identifier.
184 …  import lazy { a } from "./mod1";    // Obtain the object a from "mod1" and add a lazy identifier.
197 - Currently, lazy import cannot be executed in kit.
199 - Developers need to evaluate the impact of lazy loading.
201 …* When objects are exported, time required for the lazy import deteriorates corresponding features.
202     * Bugs occur when the **lazy** identifier is used but the module is not executed.