• Home
  • Raw
  • Download

Lines Matching full:will

113 …cess of parsing an import path, the string literal will be passed to the importPathManager which w…
114 …t still needs to be parsed (handle and avoid duplications), and this list will be requested and tr…
116will be stored in an ImportSource instance. The latter two information can be set under the dynami…
120 The import specifier list will be filled until an import directive can be found, which may contain …
126 …ortAlias, but there is a temporary exception due to stdlib sources, which will have to be handled …
127will be introduced as a result of import * as N where N is an identifier. In this case, it will be…
134will create the *ImportSpecifier* AST Node with local name, which in case of import alias it will
144 …arseImportDefaultSpecifier* will create an *ImportDefaultSpecifier* AST node with the imported ide…
154 The *ParseImportDeclarations* method itself will set the importKind member if it will met a type ke…
158 The *ETSImportDeclaration* nodes will be added to the statements list.
160 The binder component will build/validate all the scope bindings. It's not a standalone analysis; ea…
164 … the binder's BuildImportDeclaration method will be called for every *ETSImportDeclaration* nodes …
235 Single export directive allows to specify the declaration which will be exported from the current c…
259 The selective export directive is parsed in the *ETSParser::ParseExport* method, it will calls the …
285 * It will support renaming, as expected
286 … * It will checks for clashing names, when the given alias is a name, which is also exported, like:
295 …* A compile time error will be thrown, if something is being imported using its original name, but…
296 …* Similar behaviour will occur if something is being referred by its original name after being imp…
305 …all.test_func() //A compile time error will be thrown at this point, since 'test_func' has an alia…
307 * Support for exporting an imported program element will also be added at some point:
350 …* The specifiers will be parsed in the *ETSParser::ParseExport* method, which calls the *ETSParser…
351 * It will resolve the importPath in the same way as in the case of import declarations.
352 …* Instead of storing this specifiers in an *ExportNamedDeclaration* AST node, it will create an *E…
353 …* An *ETSReExportDeclaration* AST node will be created, which will contains this *ETSImportDeclara…
354 …o the binder's BuildImportDeclaration method will be called for every ETSImportDeclaration nodes w…
355 …If there is a call to a member within *A*, and cannot find it, the search will be extended with *S…
410 Since the export type directive only support exporting types, a compile time error will be thrown i…
416 export type {msg} //a CTE will be thrown here, since msg is not a type but a variable