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

Code compiled by the expression compiler should have language rules (e.g. definite assignment) applied. #549

Open
gafter opened this issue Feb 16, 2015 · 2 comments

Comments

@gafter
Copy link
Member

gafter commented Feb 16, 2015

Code compiled by the expression compiler should follow normal language rules. Specifically, for variables declared within the expression (e.g. within a lambda), it should be an error to use the variable before it has been assigned a value.

We should have unit tests that verify this is occurring.

Placing in the 1.0 (stable) milestone, as it may be a breaking change to add constraints later.

@ManishJayaswal
Copy link
Contributor

@cston is there anything we need to do here still? If not then please close.

@ManishJayaswal ManishJayaswal modified the milestones: 1.3, 1.2 Jan 27, 2016
@ManishJayaswal ManishJayaswal modified the milestones: 1.3, 2.0 (RC) May 6, 2016
@jaredpar jaredpar modified the milestones: 2.0 (RTM), 2.0 (Preview 5) Sep 9, 2016
@cston
Copy link
Member

cston commented Sep 9, 2016

See ExpressionCompilerTests.FlowAnalysis, currently skipped.

@ManishJayaswal ManishJayaswal modified the milestones: 2.1, 2.0 (RTM) Jan 4, 2017
@jinujoseph jinujoseph modified the milestones: 15.1, 15.later May 22, 2017
@jinujoseph jinujoseph modified the milestones: 15.6, Unknown Nov 3, 2017
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

5 participants