Format code better in “map of corresponding features” table #37
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
|
excellent thanks; instead, please rebase the other PR since there are comments to address |
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.
Improves formatting of the map of corresponding features section.
Git will detect a merge conflict between this and the changes in PR #36, but don’t worry, it won’t be hard to resolve. The conflict is because they make changes to adjacent table rows, “empty statement” and “null pointer”. But these changes don’t affect each other, so you can just mark the conflicting lines as “include both”, with the “null pointer” row second. If you’d rather I do this, I can rebase this PR after you accept the other PR.