Skip to content
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

[Parser] Support standalone import definitions #6191

Merged
merged 1 commit into from
Jan 2, 2024
Merged

Conversation

tlively
Copy link
Member

@tlively tlively commented Dec 20, 2023

We previously support the in-line import abbreviation, but now add support for
explicit, non-abbreviated imports as well.

@tlively
Copy link
Member Author

tlively commented Dec 20, 2023

@tlively
Copy link
Member Author

tlively commented Jan 2, 2024

Merge activity

  • Jan 2, 3:08 PM: @tlively started a stack merge that includes this pull request via Graphite.
  • Jan 2, 3:09 PM: Graphite rebased this pull request as part of a merge.
  • Jan 2, 3:36 PM: @tlively merged this pull request with Graphite.

Base automatically changed from regex-improvements to main January 2, 2024 20:08
We previously support the in-line import abbreviation, but now add support for
explicit, non-abbreviated imports as well.
@tlively tlively merged commit 5e3f81c into main Jan 2, 2024
15 checks passed
@tlively tlively deleted the parser-imports branch January 2, 2024 20:36
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
We previously support the in-line import abbreviation, but now add support for
explicit, non-abbreviated imports as well.
@gkdn gkdn mentioned this pull request Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants