| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +2 |
// We set flags to 0x80 (high bit 7 unused in quick check data) to indicate an invalid rune.0x80 means the MSB is set (the 8th)? Am I mis-reading? Is this 0-indexing the bit indicies?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
// We set flags to 0x80 (high bit 7 unused in quick check data) to indicate an invalid rune.0x80 means the MSB is set (the 8th)? Am I mis-reading? Is this 0-indexing the bit indicies?
Yeah, the comment above is using 0-indexing and I chose to be consistent.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
unicode/norm: avoid infinite loop on invalid input
Invalid characters are given a Properties with a size of 0.
The nextComposed function can enter an infinite loop when
encountering an invalid character, since it advances
its input by the (possibly 0) character size.
Rather than finding every place which might assume characters
have a non-zero size, change compInfo to return a size-1
Properties for invalid characters and use the property flags
to record validity.
Fixes golang/go#80142
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |