Document trick for testing mutable specials #52331
Merged
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
Explain how to tweak the placement test to test placement for your special when you're designing a new one.
Maleclypse
added
[Markdown]
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.
Summary
None
Purpose of change
Testing for rare placement errors in mutable specials can be difficult to do by hand. I wrote a test to help me; we should let other mappers know about it.
Describe the solution
Explain how to tweak the placement test to test placement for your special when you're designing a new one.
Describe alternatives you've considered
Making it even easier by somehow arranging matters that you don't need to recompile to run this test.
Testing
Read the rendered markdown here.
Additional context