Discard import declarations
At the moment, we do not emit bound node information yet. (See marapongo/mu#46). When that day comes we will need to decide whether import declarations are needed or, as I suspect, they can continue to be discarded safely because all dependency information is available on the bound nodes themselves. I'm leaving in a TODO in there just as a reminder to resolve this at that time.
This commit is contained in:
parent
c3027f6822
commit
3c76092d46
1 changed files with 6 additions and 10 deletions
|
@ -343,16 +343,12 @@ export class Transformer {
|
|||
return contract.fail("NYI");
|
||||
}
|
||||
|
||||
private transformImportDeclaration(node: ts.ImportDeclaration): ast.Definition {
|
||||
return contract.fail("NYI");
|
||||
}
|
||||
|
||||
private transformImportClause(node: ts.ImportClause | undefined): ast.Definition[] {
|
||||
return contract.fail("NYI");
|
||||
}
|
||||
|
||||
private transformImportSpecifier(node: ts.ImportSpecifier): ast.Definition {
|
||||
return contract.fail("NYI");
|
||||
private transformImportDeclaration(node: ts.ImportDeclaration): ModuleElement {
|
||||
// TODO[marapongo/mu#46]: we are ignoring import declarations for the time being. Eventually we need to
|
||||
// transform all dependency symbols into real MuIL references. (Today, bound node information is
|
||||
// discarded.) When that day comes (soon), import declarations will most likely still be ignored, however,
|
||||
// I am leaving this comment in here so that we can make an explicit decision about this.
|
||||
return <ast.EmptyStatement>{ kind: ast.emptyStatementKind };
|
||||
}
|
||||
|
||||
/** Statements **/
|
||||
|
|
Loading…
Reference in a new issue