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
(\a b ->TkComment (MkComment (Ann b) a)) <$ char '#'<*>
many (satisfy (`notElem` ['\r', '\n']))
Is there any reason that it doesn't support parsing of docstrings, or is it just not a use case that QFPL hasn't had need for yet (i.e. would a PR be welcomed, or potentially something to add as a milestone for a future release)?
The text was updated successfully, but these errors were encountered:
jkachmar
changed the title
Parsing and handling Docstrings (in addition to comments)
Parsing and handling of docstrings (in addition to comments)
May 2, 2019
Hey Joe - yes, docstrings aren't explicitly handled by the parser. This is because they're not a syntactic feature, they're a string literal on the first line of a function/class body. hpython doesn't ignore docstrings, they're just not considered comments.
That being said, I think we could do with functions that make it easier to create and modify docstrings. I'll think about the shape of those functions over the next few hours and check in later.
As far as I can tell
hpython
only parses standard Python comments:hpython/src/Language/Python/Internal/Lexer.hs
Lines 115 to 118 in ede398a
Is there any reason that it doesn't support parsing of docstrings, or is it just not a use case that QFPL hasn't had need for yet (i.e. would a PR be welcomed, or potentially something to add as a milestone for a future release)?
The text was updated successfully, but these errors were encountered: