Robert Nystrom
5bb9e922db
The new formatter supports opting a region of code out from being formatted. I'm applying this marker to all of the multitests since those tests are often very sensitive to formatting and easily broken. This way, anyone touching a multitest (including me when I reformat the tests) doesn't have to remember to not run the formatter on it. Unfortunately, this doesn't opt out 100# of the multitests. There are a handful of multitests that also contain "@dart=" comments and are thus formatted using the old style where the "// dart format off" marker has no effect. For those, we'll have to still be careful to not accidentally format them. Change-Id: I257d0ee1eb44eee57047be06b8520f0ccc7b56d3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/396162 Auto-Submit: Bob Nystrom <rnystrom@google.com> Commit-Queue: Erik Ernst <eernst@google.com> Reviewed-by: Erik Ernst <eernst@google.com>
31 lines
922 B
Dart
31 lines
922 B
Dart
// Copyright (c) 2013, 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.
|
|
|
|
// Formatting can break multitests, so don't format them.
|
|
// dart format off
|
|
|
|
// Test handling of unknown constructor in const expression.
|
|
|
|
class GoodClass {
|
|
const GoodClass();
|
|
}
|
|
|
|
GoodClass? GOOD_CLASS
|
|
= const GoodClass() //# 01: ok
|
|
= const GoodClass.BAD_NAME() //# 02: compile-time error
|
|
= const GoodClass("bad arg") //# 03: compile-time error
|
|
;
|
|
|
|
const BadClass BAD_CLASS = const BadClass(); //# 04: compile-time error
|
|
BadClass BAD_CLASS = const BadClass(); //# 05: compile-time error
|
|
|
|
void main() {
|
|
try {
|
|
print(GOOD_CLASS);
|
|
print(BAD_CLASS); //# 04: continued
|
|
print(BAD_CLASS); //# 05: continued
|
|
print(const BadClass()); //# 06: compile-time error
|
|
} catch (e) {}
|
|
}
|