-
Notifications
You must be signed in to change notification settings - Fork 53
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
Signature tweak to the grammar. #527
Conversation
a7883b5
to
05c0e5b
Compare
INestedModuleDeclaration CreateNestedModule(string name); | ||
|
||
IModuleMember CreateModuleMember(string source); | ||
IFSharpTypeMemberDeclaration CreateTypeMemberSignature(string source); |
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.
It seems it can also be used to create non-signature type members? If true, then maybe something like CreateTypeMember
would be a better name.
if memberSigs.IsEmpty then | ||
x.AdvanceToTokenOrRangeEnd(FSharpTokenType.END, parentRange) | ||
x.Advance() |
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 you add a parser test and/or a comment about the pending FCS fix for this, please?
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.
Hmm, I added a test but the problem is still there.
If there is nothing besides an empty nested module the parentRange
will end right before the =
token.
@nojaf Thanks a lot! |
Extracted the grammar and parser changes from #481