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.
This adds some warning text to a few sections of the main specs document to signal that we're aware of its shortcomings and are working on improving the spec. The odd formatting is me abusing github markdown's table syntax to draw some attention to the text.
So far I've just added a pretty generic notice to the intro and the sections that seem (to me) to be the most problematic: architecture, interfaces and properties.
There are other sections that need work as well, but those three need the most attention in the short term, IMO.
Questions:
Another larger question is whether we should go big and focus on #110 vs rehabilitating the existing specs.