Skip to content

[WIP] Fix https://github.com/swiftlang/swift/issues/80014 #80088

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

Conversation

nickolas-pohilets
Copy link
Contributor

@nickolas-pohilets nickolas-pohilets commented Mar 18, 2025

Failing tests:

  • test/Concurrency/async_let_isolation.swift
  • test/Concurrency/async_task_groups.swift
  • test/Concurrency/async_tasks.swift
  • test/Concurrency/issue-57376.swift
  • test/Concurrency/predates_concurrency_import.swift
  • test/Concurrency/sendable_checking.swift
  • test/Concurrency/sending_mutable_captures.swift
  • test/Concurrency/transfernonsendable.sil
  • test/Concurrency/transfernonsendable.swift
  • test/Concurrency/transfernonsendable_instruction_matching.sil
  • test/Concurrency/transfernonsendable_nonisolatedunsafe.swift
  • test/Interpreter/indirect_enum.swift
  • test/Sanitizers/asan/asan.swift
  • test/Sanitizers/asan/globals-overwrite.swift
  • test/abi/macOS/arm64/observation-asserts.swift
  • test/stdlib/Synchronization/Mutex/LockSingleConsumerStack.swift
  • validation-test/BuildSystem/swift-xcodegen.test
  • validation-test/execution/arc_36509461.swift

Note sure how to implement logic from 7c45c7d.

@nickolas-pohilets nickolas-pohilets marked this pull request as draft March 18, 2025 15:44
@@ -1247,7 +1247,12 @@ SILType SILType::removingAnyMoveOnlyWrapping(const SILFunction *fn) {
}

bool SILType::isSendable(SILFunction *fn) const {
return getASTType()->isSendableType();
switch (getCategory()) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to change the behavior of other existing callers in the compiler. I'm also not convinced this is necessary. Whether a type is loadable or address-only is an implementation detail of the type and should not be observable in the language semantics in any way.

@nickolas-pohilets
Copy link
Contributor Author

Superseded by #80745

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants