Robert Nystrom
cd5883fa85
The "@compile-error" comment is an old not-great way of defining static error tests. Change-Id: I6564643302f66c5920b38d2269c160099322560b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/296421 Reviewed-by: Jake Macdonald <jakemac@google.com> Commit-Queue: Jake Macdonald <jakemac@google.com> Auto-Submit: Bob Nystrom <rnystrom@google.com>
23 lines
877 B
Dart
23 lines
877 B
Dart
// Copyright (c) 2012, the Dart project authors. Please see the AUTHORS file
|
|
// for details. All rights reserved. Use of this source code is governed by a
|
|
// BSD-style license that can be found in the LICENSE file.
|
|
// Dart test program for testing named parameters.
|
|
// Specifying named argument for not existing named parameter is run time error.
|
|
|
|
// This test is very similar to NamedParameters3Test, but exercises a
|
|
// different corner case in the frog compiler. frog wasn't detecting unused
|
|
// named arguments when no other arguments were expected. So, this test
|
|
// purposely passes the exact number of positional parameters.
|
|
|
|
int test(int a) {
|
|
return a;
|
|
}
|
|
|
|
main() {
|
|
// 1 positional arg, as expected. Param x does not exist.
|
|
test(10, x: 99);
|
|
// ^
|
|
// [analyzer] COMPILE_TIME_ERROR.UNDEFINED_NAMED_PARAMETER
|
|
// [cfe] No named parameter with the name 'x'.
|
|
}
|