[GH-ISSUE #36] Inline Comments? #13

New issue

Open

opened 2026-05-22 22:05:09 +01:00 by JakeStanger · 2 comments

JakeStanger commented

2026-05-22 22:05:09 +01:00

Owner

Originally created by @zyansheep on GitHub (Feb 16, 2025).
Original GitHub issue: https://github.com/corn-config/corn/issues/36

It would be nice to have inline comments I think.

Something like:

$list = [ /* item1 */ item2 item3 ]

Any thoughts?

Originally created by @zyansheep on GitHub (Feb 16, 2025). Original GitHub issue: https://github.com/corn-config/corn/issues/36 It would be nice to have inline comments I think. Something like: ```corn $list = [ /* item1 */ item2 item3 ] ``` Any thoughts?

JakeStanger added the

enhancement

label

2026-05-22 22:05:09 +01:00

JakeStanger commented

2026-05-22 22:05:10 +01:00

Author

Owner

@JakeStanger commented on GitHub (Mar 5, 2025):

I've given it some thought, and yes I think this would be good to have.

@JakeStanger commented on GitHub (Mar 5, 2025): I've given it some thought, and yes I think this would be good to have.

JakeStanger commented

2026-05-22 22:05:10 +01:00

Author

Owner

@rdin777 commented on GitHub (Dec 17, 2025):

Subject: Analysis of existing COMMENT rule in grammar.pest

"Hi everyone!

I've been looking into this issue and noticed that the src/grammar.pest file already contains a COMMENT rule: COMMENT = _{ "//" ~ (!"\n" ~ ANY)* }.

In the Pest parser, WHITESPACE and COMMENT rules are typically implicit between other rules. However, I’d like to clarify a few points to better understand the current blocker:

Inline Behavior: Does the current implementation fail when a comment is placed on the same line as a value (e.g., key = "value" // comment)?

Atomic Rules: Are there any specific atomic rules (like strings or paths) where the comment might be interfering or failing to be ignored?

Parser Integration: Is the COMMENT rule correctly handled in the src/parser.rs (or equivalent) when generating the AST, or is it currently being skipped entirely?

I'm interested in helping to fix the implementation if the foundation is already there. Looking forward to your thoughts!"

@rdin777 commented on GitHub (Dec 17, 2025): Subject: Analysis of existing COMMENT rule in grammar.pest "Hi everyone! I've been looking into this issue and noticed that the src/grammar.pest file already contains a COMMENT rule: COMMENT = _{ "//" ~ (!"\n" ~ ANY)* }. In the Pest parser, WHITESPACE and COMMENT rules are typically implicit between other rules. However, I’d like to clarify a few points to better understand the current blocker: Inline Behavior: Does the current implementation fail when a comment is placed on the same line as a value (e.g., key = "value" // comment)? Atomic Rules: Are there any specific atomic rules (like strings or paths) where the comment might be interfering or failing to be ignored? Parser Integration: Is the COMMENT rule correctly handled in the src/parser.rs (or equivalent) when generating the AST, or is it currently being skipped entirely? I'm interested in helping to fix the implementation if the foundation is already there. Looking forward to your thoughts!"

JakeStanger referenced this issue

2026-05-22 22:05:14 +01:00

[PR #16] [MERGED] refactor: improve error handling and code quality #27

JakeStanger referenced this issue

2026-05-22 23:00:38 +01:00

[GH-ISSUE #13] Improved error handling #7