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

Support for nullables #23

Open
danielgindi opened this issue Jul 29, 2016 · 1 comment
Open

Support for nullables #23

danielgindi opened this issue Jul 29, 2016 · 1 comment

Comments

@danielgindi
Copy link

If it's a Bool (vs. bool), then first a extra byte of != null should be emitted, and then if it's not null, emit the byte representing the value.
Same goes for a String - emit a byte, and if not null emit the string.
And for any other type...

Thanks :-)

@sockeqwe
Copy link
Owner

sockeqwe commented Jul 29, 2016

I might be wrong, but null on objects is already handled by the framework. So null for String should work, doesn't it?

Regarding wrappers like Bool , Double, Integer and so on, yes, null support is missing for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants