Skip to content

Conversation

@leonlan
Copy link
Member

@leonlan leonlan commented Dec 9, 2025

Closes #132.

Copy link
Member

@N-Wouda N-Wouda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment on lines +79 to 80
if ":" in next_line and "_SECTION" not in next_line:
raise ValueError("Specification presented after section.")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking out loud, but what about EOF:. Should we let that be OK?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strictly speaking, the paper includes EOF:. But it's such a weird case that I doubt that anyone will have problems with this. If they do, they can make a new issue :-).

@leonlan leonlan merged commit cc0187e into main Dec 9, 2025
4 checks passed
@N-Wouda N-Wouda deleted the parse-section-first branch December 9, 2025 21:24
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.

Unexpected parsing failure when a section header contains a trailing colon

3 participants