-
-
Notifications
You must be signed in to change notification settings - Fork 671
Allow keywords in named import/export syntax #107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
dcodeIO
merged 3 commits into
AssemblyScript:master
from
alangpierce:allow-keywords-in-named-exports
May 13, 2018
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
(module | ||
(type $i (func (result i32))) | ||
(memory $0 1) | ||
(export "default" (func $named-export-default/get3)) | ||
(export "memory" (memory $0)) | ||
(func $named-export-default/get3 (; 0 ;) (type $i) (result i32) | ||
(i32.const 3) | ||
) | ||
) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
function get3(): i32 { | ||
return 3; | ||
} | ||
|
||
export {get3 as default}; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
(module | ||
(type $i (func (result i32))) | ||
(global $HEAP_BASE i32 (i32.const 4)) | ||
(memory $0 1) | ||
(export "default" (func $named-export-default/get3)) | ||
(export "memory" (memory $0)) | ||
(func $named-export-default/get3 (; 0 ;) (type $i) (result i32) | ||
(return | ||
(i32.const 3) | ||
) | ||
) | ||
) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
(module | ||
(type $i (func (result i32))) | ||
(memory $0 1) | ||
(export "getValue" (func $named-import-default/getValue)) | ||
(export "memory" (memory $0)) | ||
(func $named-export-default/get3 (; 0 ;) (type $i) (result i32) | ||
(i32.const 3) | ||
) | ||
(func $named-import-default/getValue (; 1 ;) (type $i) (result i32) | ||
(call $named-export-default/get3) | ||
) | ||
) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
import { | ||
default as get3 | ||
} from "./named-export-default"; | ||
|
||
export function getValue(): i32 { | ||
return get3(); | ||
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
(module | ||
(type $i (func (result i32))) | ||
(global $HEAP_BASE i32 (i32.const 4)) | ||
(memory $0 1) | ||
(export "getValue" (func $named-import-default/getValue)) | ||
(export "memory" (memory $0)) | ||
(func $named-export-default/get3 (; 0 ;) (type $i) (result i32) | ||
(return | ||
(i32.const 3) | ||
) | ||
) | ||
(func $named-import-default/getValue (; 1 ;) (type $i) (result i32) | ||
(return | ||
(call $named-export-default/get3) | ||
) | ||
) | ||
) |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this become an
IdentifierHandling
option onskip()
, maybe? :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense, yeah this copied function is a bit ugly. I guess it felt a bit weird given the special case in
skip
.How about this: I get rid of the special case in
skip
and specify it using an optional param like you suggested. Then, to make the common case the most natural to write, I'll makeskipIdentifier
as a shorthand forskip(Token.IDENTIFIER, IdentifierHandling.PREFER)
and keepskipIdentifierName
as a shorthand forskip(Token.IDENTIFIER, IdentifierHandling.ALWAYS)
. Let me know what you think.