You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discovered via fuzzing using the dev.fuzz branch: CL 308611 optimized the scanning of identifiers, but inadvertently changed the handling of zero-bytes.
For example, when scanning the following bad input, go 1.17 is missing an error "illegal character NUL", though it does scan the same token stream (including a follow-up error for "illegal character U+0000"): "package p;e\x00"
This might be an improvement, but we should not unintentionally change this behavior for 1.17. The fix is trivial.
Discovered via fuzzing using the dev.fuzz branch: CL 308611 optimized the scanning of identifiers, but inadvertently changed the handling of zero-bytes.
For example, when scanning the following bad input, go 1.17 is missing an error "illegal character NUL", though it does scan the same token stream (including a follow-up error for "illegal character U+0000"): "package p;e\x00"
This might be an improvement, but we should not unintentionally change this behavior for 1.17. The fix is trivial.
CC @griesemer
The text was updated successfully, but these errors were encountered: