Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow NUL character in Strings #18100

Closed
iposva-google opened this issue Apr 8, 2014 · 2 comments
Closed

Allow NUL character in Strings #18100

iposva-google opened this issue Apr 8, 2014 · 2 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@iposva-google
Copy link
Contributor

See issue #18090 for original report.

@DartBot
Copy link

DartBot commented Apr 24, 2014

This comment was originally written by @mhausner


We handle strings with escaped nul characters right now when re-generating source code.
https://codereview.chromium.org/254553003/

@iposva-google iposva-google added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. labels Apr 24, 2014
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@rmacnak-google
Copy link
Contributor

Not sure which this bug was about, but strings allow internal NULs and the --print-sources feature was removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

4 participants