PEP484 support and bugfixes #126
Closed
Conversation
This file contains 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
Example: (b [0])
…it can understand PEP484 type annotations.
|
How is this PR different from #115 ? I'm trying to make a fork of baron with all the open PRs and it seems these two PRs overlap.. |
|
No difference. I didn't see that before submitting this PR. |
|
Cool. Then I’ll use the other one for my fork.
… On 24 Jul 2018, at 15:58, kyleatmakrs ***@***.***> wrote:
No difference. I didn't see that before submitting this PR.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Merge by hand, thx a lot :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows baron to parse files with PEP484 type annotations.
Also a bugfix for handling endl inside groups:
"(a
[0])"