Introduce semantics-aware parsing of documentation #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status: Allowing time for feedback before release
Instead of reiterating myself here, the best place to see these in action is over in wjakethompson/measr#52, which was the impetus for these changes.
That package is quite comprehensive in its documentation, so it gives me some pretty strong confidence that things are working as intended, but nevertheless these changes are substantial and would meaningfully increase the scope of this package and its complexity.
To make sure that I'm not biting off more than I can handle, I think it's best to make sure those changes are going to be satisfactory in use over in
measrbefore rolling them out more broadly.