You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we assume that a single line comment ends with a line feed. We need to change this so that a carriage return also means an end of comment (or both \r\n). This way we match the semantics of Json.NET as well.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback on my PR @ahsonkhan
I hadn't realized JSON.Net would continue to process text as a single-line comment between a \r and \n. I'll be able to take another go at this within the next few days.
I have a question though. If \r does not end a single-line comment when it is followed (at some point) by a \n, would that make checking for \r to end a single-line comment redundant? Or are you saying we should treat \r as a comment terminator only if it is not followed (at some point) by a \n?
Currently, we assume that a single line comment ends with a line feed. We need to change this so that a carriage return also means an end of comment (or both \r\n). This way we match the semantics of Json.NET as well.
The text was updated successfully, but these errors were encountered: