forked from apple/swift
-
Notifications
You must be signed in to change notification settings - Fork 28
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
[pull] swiftwasm from main #5220
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t` part from `self.init`
…nherit the message and renaming from the initializer of the superclass
rdar://99495048
Both of these IRGen tests expect to see internal details from resilient modules at build time. Deserialization safety hides that information, let's disable it to preserve the desired behavior.
Resolves rdar://94436652
The SwiftDiagnostics module within swift-syntax has a diagnostic pretty-printer that does a nice rendering of the source code with diagnostics placed inside gaps between the code lines. Introduce another `-diagnostic-style` argument, `swift-syntax`, to bridge from the pretty-printed C++ diagnostics over to the swift-syntax diagnostics engine.
Type wrappers were invoking CustomAttrDeclRequest with a decl context of the attached nominal type rather than its decl context, so the request was invoked twice for the same custom attributes with different decl contexts.
invalid macro attributes in `findMacroForCustomAttr`.
…c-style [Diagnostics] Add a swift-syntax diagnostic style
type checking macro attribute arguments into two different requests.
The flag is not supported by current clang.
…otocol_witness_table_2nd Really disable test IRGen/relative_protocol_witness_table.swift
…t_fnptr Disable the test IRGen/fnptr.swift
…table path as parameter This new version takes the path to the compiler executable as a parameter, in order for libSwiftScan to compute compiler-relative portions of runtimeLibraryPaths, runtimeResourcePath. V1, without knowing the path to the compiler executable, produced incomplete sets of these paths.
…ializers SILGen/Sema: Add `@_backDeploy` support for constructors
… allocation testing and making it less brittle (apple#63095)
The impact should be very high because the whole body is skipped if the builder does not support some of the operations, otherwise the fix would interfere with result builders that do support operations but have syntactic issues in the body. Resolves: rdar://89880662
[NFC] Require asserts for new variadic generics test.
[libSwiftScan] Add V2 target info query API that takes compiler executable path as parameter
If a unit test is miswritten in the sense that the test expects an instance of one type by an instance of some other type is specified, print that out.
rdar://104021173
[BuilderTransform] Increase impact of unhandled statement fix
Per the existing proposal, we're not supporting move-only reference types right now.
…es, optionals Resolves rdar://103187206
[Serialization] Enable deserialization safety by default
Not aliasing the stdlib should allows it to be used in inlinable code. Since builtin isn't imported explicitly, references to it shouldn't use the alias. rdar://104582241
Resolves rdar://104576016
[Sema] Record specify contextual type for nil in placeholder context
[Test] Print helpful info on malformed unit test.
Dropping dependency on SwiftOnoneSupport is typically not an ABI-breaking change. rdar://104567396
A lot of existing regression tests rely on there being some form of move-only classes, despite them being something that will not be available to users (and not complete). This change introduces a `MoveOnlyClasses` experimental feature so that those tests don't need to be fully rewritten just yet. You need to include `-enable-experimental-feature MoveOnlyClasses` along with `-enable-experimental-move-only` to get move-only classes.
Limit `@_moveOnly` to structs and enums
…gnostic-in-swift-interface Sema: Avoid diagnosing over-availability in swiftinterfaces
[ModuleInterface] Don't alias the stdlib or builtin modules in alias module names mode
Fix apple#57354: Fix-it for deprecated initializers removes the `.init` part from `self.init`
…iesWhenPrinting [Compile Time Constant Extraction] Print desugared array, dictionary, optional types
…l feature as requiring assertions Experimental features are not available in non-assert compilers, so these tests fail for release compilers.
…-asserts [test] Mark moveonly tests that use the `MoveOnlyClasses` experimental feature as requiring assertions
[cxx-interop] Add benchmark for std::set conversion to a Swift collection
[doc] Fix SIL.rst enum initialization example
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )