forked from swiftlang/swift
-
Notifications
You must be signed in to change notification settings - Fork 30
[pull] master from apple:master #38
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
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
[Diagnostics] Unsatisfied requirement `in reference` diagnostics expe…
Fix EscapeAnalysis value_to_bridge_object and strong_copy_unowned_value.
Add EscapeAnalysis verification to catch unmapped SILValues.
…9396) Add `SILFunctionType::getAutoDiffDerivativeFunctionType`. It computes the derivative `SILFunctionType` for an "original" `SILFunctionType`, given: - Differentiability parameter indices - Differentiability result index - Derivative function kind - Derivative function generic signature (optional) - Other auxiliary parameters Add doc comments explaining typing rules, preconditions, and other details. Partially resolves TF-1124. Unblocks upstreaming other SIL differentiable programming infrastructure.
…aram [AutoDiff upstream] Add `@noDerivative` flag to `SILParameterInfo`.
[Gardening] Update the utils/backtrace-check script to use more modern Python formatting.
[Function builders] Add support for "if #available".
We’ll want to pull these back out for diagnostic purposes.
Set the contextual type of conditional expressions (to Bool) with the "condition" purpose so we get customized diagnostics for mistakes such as if x.property = y { } Prior to this, we'd get generic "() isn't convertible to Bool" diagnostic. Now we get use of '=' in a boolean context, did you mean '=='?
Turn off speculative devirtualization by default. Add a flag to support enabling the pass. Fixes rdar://58778959 and rdar://58429282
[Gardening] Remove the unused utils/build-overlay script.
…cript [Gardening] Remove the unused utils/error_enum_to_cases.pl script.
…ript [Gardening] Remove the unused utils/guard-malloc-swift script.
[Build System: build-script] Allow users to enable distcc via the USE_DISTCC environment variable.
This adds support for building PythonKit as a package as part of the toolchain build.
When doing header interface generation, we interpret clang command-line arguments in `initInvocationByClangArguments` and attempt to setup a matching Swift compiler invocation. One important argument is the module cache, but clang will only interpret `-fmodules-cache-path` if modules are enabled (typically with `-fmodules`). While the header itself might not need modules, Swift will import its own shims module and during testing this needs to honour lit's provided cache. So we add -fmodules in sourcekitd-test anytime we add -fmodules-cache-path. rdar://58836540
…/closed over parameters.
…unction-builders [Constraint system] Set the contextual type for condition expressions.
build: remove `SWIFT_BUILD_STDLIB` check (NFC)
stdlib: move Dictionary's find functions into __RawDictionaryStorage.
[sourcekitd-test] When setting -fmodules-cache-path also set -fmodules
[CSDiag] Start chipping away at FailureDiagnosis::diagnoseAmbiguity
…expr-csdiag [Diagnostics] Remove obsolete FailureDiagnosis::visitIdentityExpr from CSDiag
…lMembers() and lazy loading Lazy loading checked if the ClangDecl was hidden, but loading all members did not. Let's make loadAllMembers() behave like the lazy path, and fix some of the mock SDKs in the test suite.
Metadata prespecialization will be available after Swift 5.2.
…wift which replaces the existing module from swift_build_support.
They don't have a context and therefore are not consumed. Fixes a failing assert. rdar://59046275
[Constraint system] Make solver less expression-centric, part N/M
[Diagnostics] Port name shadowing diagnostics
…lyEscaping_c_closure SILGen: Fix withoutActuallyEscaping of 'c' closures
[Build System: build-script] Adds a new cache_utils module to build_swift which replaces the existing module from swift_build_support.
…ault-5 [Incremental] Turn type-body-fingerprints on-by-default
The static variants should use the same flags as the dynamic variants. We missed the name conversion in the variable computation causing the static and dynamic builds to diverge.
The change to introduce a "top-level" bit for VarDecls requires a module format version bump, per #29024. Fixes rdar://problem/59078925
This reverts commit be37141. Add a small fix in the dereferencing.
…ersion [Serialization] Bump module format version.
Fixes <rdar://problem/58887618>.
Type checking an expression pattern had a hack to work around some diagnostics issues with conditions. These issues have been addressed by the new diagnostic infrastructure, so remove this unnecessary use of ExprTypeCheckListener and check the expression pattern condition using… typeCheckCondition().
…e solver Rather than use an ExprTypeCheckListener subclass to introduce the autoclosure expression, do it at the end of solving.
…class-methods AST: Fix computeSelfParam() to respect __consuming on class methods
This flag is recoverable from the contextual type purpose; don’t duplicate the logic.
This is always set along with SubExpressionDiagnostics, so use that for both purposes. That flag will go away when `CSDiag.cpp` goes away.
build: correct the handling for the static variants
A contextual type purpose, that is, so it captures more about what the entity is that is being solved.
Revert "Revert "build: simplify version tracking logic""
MaxDesiatov
pushed a commit
that referenced
this pull request
Feb 13, 2020
[pull] swiftwasm from apple:master
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]. Want to support this open source service? Please star it : )