[SE-0494] small trivially identical updates #3029
Open
+42
−19
Conversation
This file contains hidden or 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
xwu
added
editorial
Contributor
|
One might say, trivial updates 😉 |
vanvoorden
force-pushed
the
trivially-identical-updates
branch
from
e4e000b to
236d5f9
Compare
Contributor
Author
|
@rjmccall All implementation diffs have landed now in latest |
vanvoorden
force-pushed
the
trivially-identical-updates
branch
from
236d5f9 to
84f8fb9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Some small updates to the 0494 proposal:
The status is now implemented and on track for 6.4.
The implementation links include our changes to
SpanandBuffertypes.Some small formatting fixes. GH markdown is a little more forgiving than canonical CommonMark spec. We can change a little formatting like adding extra line breaks before lists and angle brackets around links to better support both specs.
Also added a few extra line breaks in the sample code utility to make it easier to see the effects of the proposal.
The
UTF8Spantype was listed in both "Detailed Design" and "Future Directions". This is an error. When we made the decision to implementUTF8Spanin this proposal it should have been removed from "Future Directions".