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

Jump to bottom

Warning 50 triggers on "empty" files #7138

Closed
vicuna opened this issue Feb 8, 2016 · 1 comment
Closed

Warning 50 triggers on "empty" files #7138

vicuna opened this issue Feb 8, 2016 · 1 comment
Assignees
@lpw25
Labels
bug lexing-and-parsing

Comments

@vicuna
Copy link

vicuna commented Feb 8, 2016

Original bug ID: 7138
Reporter: @trefis
Assigned to: @lpw25
Status: resolved (set by @gasche on 2018-05-11T20:33:55Z)
Resolution: fixed
Priority: normal
Severity: minor
Fixed in version: 4.07.0+dev/beta2/rc1/rc2
Category: lexing and parsing
Has duplicate: #7701
Monitored by: @hcarty

Bug description

If a .mli file contains nothing but a doc comment, warning 50 will trigger as the comment is considered unattached.

Additional information

Adding code after the comment makes the warning go away.

Adding only blank lines after the comment doesn't make the warning go away.

Adding two (or more) blank lines before the comment makes the warning go away.

Adding only one blank line before the comment doesn't make the warning go away.
@vicuna
Copy link
Author

vicuna commented Feb 9, 2016

Comment author: @lpw25

I had a look at this but it is not an easy fix so it will have to wait for 4.04.

@vicuna vicuna closed this as completed May 11, 2018
@vicuna vicuna mentioned this issue Mar 14, 2019
Closed
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lpw25 lpw25

Labels
bug lexing-and-parsing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lpw25 @vicuna