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

parse nullable types #51

Open
degory opened this issue Jul 27, 2017 · 1 comment
Open

parse nullable types #51

degory opened this issue Jul 27, 2017 · 1 comment

Comments

@degory
Copy link
Owner

degory commented Jul 27, 2017

  x: int?;
  y: String?;

Ultimately want nullable-ness to be opt-in across all value and reference types and all accesses through nullables to require a preceding successful has-value operation (?), provable via data-flow analysis.
Can't implement this until we have a real middle-end - even foregoing the data-flow analysis, we cannot determine what legacy L to emit without symbol type information, as required behaviour would differ for value types vs reference types (value types need wrapping in a struct, with a has-value flag, reference types can stay as is, with null representing has-no-value)
Not sure in the interim that there's much point in bothering to parse this?

@degory degory added this to the parser complete milestone Jul 27, 2017
@degory degory self-assigned this Jul 27, 2017
@degory
Copy link
Owner Author

degory commented Jul 26, 2020

Nice to have but can wait until after bootstrap

@degory degory added the on hold label Jul 26, 2020
@degory degory removed this from the parser complete milestone Jul 26, 2020
@degory degory removed their assignment Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant