Navigation Menu

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

It is a compile-time error if e refers to the name v or the name v=. #6871

Closed
scheglov opened this issue Nov 22, 2012 · 8 comments
Closed

It is a compile-time error if e refers to the name v or the name v=. #6871

scheglov opened this issue Nov 22, 2012 · 8 comments
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@scheglov
Copy link
Contributor

See latest spec draft.

FAILED: dartc-none release_ia32 language/block_scope_test
Expected: pass
Actual: fail

stdout:
(Ignoring unrecognized flag: --package-root=xcodebuild/ReleaseIA32/packages/)

stderr:
ERROR|RESOLVER|VARIABLE_REFERENCES_SAME_NAME_IN_INITIALIZER|file:/Users/scheglov/Source/Dart/dart/tests/language/block_scope_test.dart|8|13|3|Initializer of variable "foo" cannot refer to the name "foo"
     7: void testShadowingScope1() {
     8: var foo = foo();
                    ~~~
ERROR|RESOLVER|VARIABLE_REFERENCES_SAME_NAME_IN_INITIALIZER|file:/Users/scheglov/Source/Dart/dart/tests/language/block_scope_test.dart|14|15|3|Initializer of variable "foo" cannot refer to the name "foo"
    13: {
    14: var foo = foo() + 444;
                      ~~~
ERROR|RESOLVER|VARIABLE_REFERENCES_SAME_NAME_IN_INITIALIZER|file:/Users/scheglov/Source/Dart/dart/tests/language/block_scope_test.dart|46|17|3|Initializer of variable "foo" cannot refer to the name "foo"
    45: if (true) {
    46: var foo = foo() + 444;
                        ~~~
ERROR|RESOLVER|VARIABLE_REFERENCES_SAME_NAME_IN_INITIALIZER|file:/Users/scheglov/Source/Dart/dart/tests/language/block_scope_test.dart|53|17|3|Initializer of variable "bar" cannot refer to the name "bar"
    52: if (true) {
    53: var bar = bar() + 444;
                        ~~~
Compilation failed with 4 problems.

Command line: xcodebuild/ReleaseIA32/analyzer/bin/dart_analyzer --ignore-unrecognized-flags --package-root=xcodebuild/ReleaseIA32/packages/ --error_format machine /Users/scheglov/Source/Dart/dart/tests/language/block_scope_test.dart

@anders-sandholm
Copy link
Contributor

Removed this from the M2 milestone.
Added this to the M3 milestone.

@anders-sandholm
Copy link
Contributor

Removed this from the M3 milestone.
Added this to the M4 milestone.

@larsbak
Copy link

larsbak commented May 28, 2013

Removed this from the M4 milestone.
Added this to the M5 milestone.

@kasperl
Copy link

kasperl commented Jun 4, 2014

Removed this from the M5 milestone.
Added this to the 1.6 milestone.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-1.6 label.

@scheglov scheglov added Type-Defect area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). labels Aug 4, 2014
@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed triaged labels Feb 29, 2016
@natebosch
Copy link
Member

I don't follow the problem - is this about a failing test? Is it still failing?

@scheglov
Copy link
Contributor Author

scheglov commented Sep 1, 2018

Yes, this was about a failing test.
The test does not exist anymore, the issue is not referenced anywhere in SDK codebase.
So, I think we can close it as obsolete.

@scheglov scheglov closed this as completed Sep 1, 2018
@scheglov scheglov added the closed-obsolete Closed as the reported issue is no longer relevant label Sep 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

6 participants