Skip to content

[concurrency] UnspecifiedMeansMainActorIsolated tests as require asserts #76616

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

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions test/Concurrency/assume_mainactor.swift
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
// RUN: %target-swift-frontend -swift-version 6 -emit-silgen -enable-experimental-feature UnspecifiedMeansMainActorIsolated %s | %FileCheck %s
// RUN: %target-swift-frontend -swift-version 6 -emit-sil -enable-experimental-feature UnspecifiedMeansMainActorIsolated %s -verify

// REQUIRES: asserts

// READ THIS! This test is meant to FileCheck the specific isolation when
// UnspecifiedMeansMainActorIsolated is enabled. Please do not put other types
// of tests in here.
Expand Down
2 changes: 2 additions & 0 deletions test/Concurrency/assume_mainactor_typechecker_errors.swift
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
// RUN: %target-swift-frontend -swift-version 6 -emit-sil -enable-experimental-feature UnspecifiedMeansMainActorIsolated %s -verify

// REQUIRES: asserts

// READ THIS! This test is meant to check the specific isolation when
// UnspecifiedMeansMainActorIsolated is enabled in combination with validating
// behavior around explicitly non-Sendable types that trigger type checker
Expand Down