Skip to content
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

[rebranch] Merge main -> rebranch #69293

Merged
merged 82 commits into from
Oct 20, 2023
Merged

Conversation

bnbarham
Copy link
Contributor

Conflicts:

  • lib/AST/TypeCheckRequests.cpp renamed isMoveOnly which requires
    a static_cast on rebranch because Optional is now a std::optional

Also fixed IsEscapableRequest::getCachedResult which needs a similar static_cast.

hyp and others added 30 commits September 29, 2023 13:52
…d from a derived class synthesized method

The use of a synthesized C++ method allows us to avoid making a copy of self when invoking the base method from Swift
If tuple element is anchored on an assignment, we need to look
at the source of the assignment to find tuple expression the
element belongs to.
…ement failure

Only simplified locator points to the right underlying expression.

Resolves: rdar://116122902
…ibleOrNone to avoid detaching doccomments from their declarations
…-elimination and dead-store-elimination.

Instead of having a budget for each optimized load or store, provide a budget for the whole function.
Fixes a build time problem.

rdar://116877696
Always print the real module name for references in private
swiftinterfaces, ignoring export-as declarations. Keep using the
export-as name for the public swiftinterface only.

The flag `ModuleInterfaceExportAs` used to enable this behavior and
we're removing it to make it the default.

rdar://115922907
…d or subscript from a derived class synthesized method

The use of a synthesized C++ method allows us to avoid making a copy of self when accessing the base field or subscript from Swift
…t a retainable FRT value

This matches the semantics of accessing the same field from the base class
Passing the flags `-enable-experimental-feature ModuleInterfaceExportAs`
has no effect anymore, test that it's not reported as an error.
Optimizer: better handling of the complexity budget in redundant-load-elimination and dead-store-elimination
Introduce the upcoming feature `FullTypedThrows`. When enabled, infer
the error type of a `throw` statement based on its original type,
instead of always being `any Error`. This is technically a
source-breaking change, hence the upcoming feature flag.
Older compilers don't have the copy-elision of newer C++ compilers,
resulting in an error message when returning a non-copyable type. Move
llvm::Error instead of copying it.
…ed-accessor

[cxx-interop] Use a synthesized C++ method when invoking a base metho…
…overlays aren't being built

Allow for the overlays to not be built in Darwin by respecting SWIFT_BUILD_SDK_OVERLAY.
Add `swift-syntax-lib` component to the distribution set.
For testing compiler support until we have the ~Escapable syntax.
This will allow NonEscapable types to be returned from a function.
If SILGen emitted a marker, that ought to be indication enough that move only checking
is necessary.
…by-default

ModuleInterface: Always ignore export-as for printing references in private swiftinterfaces
…option

[embedded] Don't gate embedded stdlib build behind SWIFT_BUILD_STDLIB
@bnbarham
Copy link
Contributor Author

@swift-ci please smoke test

@shahmishal shahmishal merged commit a2c760d into apple:rebranch Oct 20, 2023
0 of 3 checks passed
@bnbarham bnbarham deleted the 20231019-merge-main branch October 23, 2023 20:36
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.

None yet