Test runner doesn't use experiments in analysis_options.yaml

MCVE

lib/foo.dart

typedef Foo = String;

Foo foo(){
  return 'foo';
}

test/foo_test.dart

import 'package:dart_code_3243/foo.dart';
import 'package:test/test.dart';

void main() {
  test('foo', () {
    expect(foo(), equals('foo'));
  });
}

analysis_options.yaml

include: package:pedantic/analysis_options.yaml

analyzer:
  enable-experiment:
    - nonfunction-type-aliases

pubspec.yaml

name: dart_code_3243
description: An MCVE for Dart-Code/Dart-Code issue 3243.

environment:
  sdk: ">=2.13.0-0 <3.0.0"

dev_dependencies:
  pedantic: ^1.9.0
  test: ^1.16.8

Error message when clicking run tests button

Failed to load "test/foo_test.dart":
Unable to spawn isolate: lib/foo.dart:1:13: Error: Can't create typedef from non-function type.
typedef Foo = String;

Expected:

it uses analysis_options.yaml to enable experiments.

Request for clarification

Is this intended behavior? Is there any way to enable experiments across all of Dart-Code’s features including running/debugging/analyzing/testing?

[leafpetersen]

Yes that is correct. We don’t want to make the compilers have to look for and read analysis_options.yaml, so I don’t think we would go this route. The experiment flags are intentionally somewhat manual to use, but there has been some discussion of ways to make trying out experimental features and providing feedback easier (without giving up our ability to make breaking changes to experimental features). I think @jakemac53 may have had some ideas there that might be worth revisiting at some point.

[DanTup]

I think this expected - the experiment is only read by the analyzer, not the VM when you run the code.

I don’t know if there’s a single way you can enable this for both - perhaps @leafpetersen or @mit-mit may know?