在“有效飞镖”之后捕获错误和异常的正确方法是什么？

Question

此代码示例

import 'package:flutter_test/flutter_test.dart';

void main() {
  const one = 1;
  String oneAsString() => one as String;

  test('Make sure it fails', () {
    var s;
    var _e;
    try {
      s = oneAsString();
    } on Error catch (e) {
      _e = e;
    }
    expect(s == null, true, reason: 'should fail');
    expect(_e == null, false, reason: 'error or exception should be returned');
  });

  test('Catchin Error', () {
    var _e;
    try {
      oneAsString();
    } on Error catch (e) {
      _e = e;
    }
    expect(_e is Error, true, reason: 'should be an error');
  });

  test('Catchin Exception', () {
    var _e;
    try {
      oneAsString();
    } on Exception catch (e) {
      _e = e;
    }

    expect(_e is Exception, true, reason: 'should be an exception');
  });

  test('Why not BOTH', () {
    var _e;
    try {
      oneAsString();
    } on Error catch (e) {
      _e = e;
    } on Exception catch (e) {
      _e = e;
    }

    expect(_e is Error, true, reason: 'should be an error');
    expect(_e is Exception, false, reason: 'should NOT be an exception');
  });
}

输出这个结果

00:02 +2 -1: Catchin Exception [E]                                                                                                                                                                          
  type 'int' is not a subtype of type 'String' in type cast
  test/widget_test.dart 5:31   main.oneAsString
  test/widget_test.dart 31:18  main.<fn>
  
00:02 +3 -1: Some tests failed.

最安全的方法似乎是 Why not BOTH，但遵循 effective dart
（使用包 effective_dart 强制执行）
分析抱怨 avoid_catching_errors

DON'T explicitly catch Error or types that implement it.

Errors differ from Exceptions in that Errors can be analyzed and prevented prior to runtime. It should almost never be necessary to catch an error at runtime.

BAD:

try { somethingRisky(); } on Error catch(e) { doSomething(e); } GOOD:

try { somethingRisky(); } on Exception catch(e) { doSomething(e); }

如果我简单地做

try {} catch (e) {}

分析器抱怨 avoid_catches_without_on_clauses

AVOID catches without on clauses.

Using catch clauses without on clauses make your code prone to encountering unexpected errors that won't be thrown (and thus will go unnoticed).

BAD:

try { somethingRisky() } catch(e) { doSomething(e); } GOOD:

try { somethingRisky() } on Exception catch(e) { doSomething(e); }

捕获两者的正确方法是什么Error and Exception？

Answer 1

在 r/FlutterDev discord

上重新发布 @Miyoyo 的答案

Optimally? You do not catch error
Just, at all
Remember effective dart is Guidelines
Using them as gospel will make some things impossible
Catching error is deliberately made to be "not according to guidelines"

因为你不应该那样做

对于我的用例，我将添加

// ignore_for_file: avoid_catching_errors

在“有效飞镖”之后捕获错误和异常的正确方法是什么？

What is the correct way to catch both Error and Exception following `effective dart`?

error-handling

exception

dart

dart-analyzer

flutter