Skip to content

Fix merge conflict with master #667

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 48 commits into from
Apr 14, 2020
Merged

Fix merge conflict with master #667

merged 48 commits into from
Apr 14, 2020

Conversation

MaxDesiatov
Copy link

The conflict resolution itself was trivial, the main breakage source was the introduction of _add_target_variant_c_compile_link_flags in AddSwiftStdlib.cmake, which is where _WASI_EMULATED_MMAN had to be moved from _add_host_variant_c_compile_link_flags in AddSwift.cmake.

roop and others added 30 commits February 11, 2020 06:14
Add a note to the README that `update-checkout` does not support non-ASCII characters in the path to `swift-source`.
Curried functions were removed in 2016 in 983a674.
…in their parameter lists.

Resolves rdar://problem/61461022
This allows us to start splitting up the swift and C/C++ specific paths.
Unfortunately, the types are not imported through the clang importer.
Add them to the overlay for use in applications.
…ame.

This change makes us treat it exactly as we do 'init'. We don't allow renaming the base name,
and don't fail if the basename doesn't match for calls.

Also:
  - explicit init calls/references like `MyType.init(42)` are now reported with
    'init' as a keywordBase range, rather than nothing.
  - cursor info no longer reports rename as available on init/callAsFunction
    calls without arguments, as there's nothing to rename in that case.
  - Improved detection of when a referenced function is a call (rather than
    reference) across syntactic rename, cursor-info, and indexing.

Resolves rdar://problem/60340429
Add the ShellCore module to the Windows SDK modulemap.
Platform: add ShellCore to WinSDK modulemap
WinSDK: add some constants for the SDK overlay
The `line-directive-tool` is Python3 compliant.  Use the Python3
interpreter to execute this tool.
[Index][SR-9567] Allow unavailable decls to be walked
…-callAsFunction

[IDE][Refactoring] Handle 'callAsFunction' specially in syntactic rename
[SourceKit/CodeFormat] Column-align enum element decls and the items in their parameter lists.
Correct the maximal floating point width.  Although technically, Android
could support FP128 on AArch64, Swift does not currently support FP128.
For now, ensure that we use FP64 on Android.
Removed a description of curried functions
To ease the burden on the client, ignore some generic requirements involving
Self. For example, `Self: P` where we already know that `Self` conforms to `P`.

An example case:

```
public struct S: Equatable {
  public static func ==(lhs: S, rhs: S) -> Bool { ... }
}
```

`!=` is defined in terms of `Self` and the default implementation has a `Self:
Equatable`. For the purposes of documentation, it's not necessary to specify
that again on the page of documentation for `!=`.

rdar://60963924
build: duplicate and rename the `_add_variant_*` functions
CodaFi and others added 18 commits April 13, 2020 13:59
CocoaError.Code.fileReadUnknown conflicts with the CHECK-NOT line here.
We should be checking more specifically for UnknownBlock and UnknownCode
anyways.

rdar://53284293
stdlib: android does not support FP80
…3924-ignore-some-self-reqs

[SymbolGraph] Ignore some Self requirements
…mcachedoperaiton

[CodeCompletion][NFC] Fix typo
build: explicitly execute `line-directive-tool` with Python3
Move the source files from ParserSIL into the SIL library and remove the
ParserSIL library. ParsersSIL doesn't need to be its own library and this change will
simplify our builds.
contextual type for property wrapper initialization
…(unsafeUninitializedCapacity:initializingWith:) (swiftlang#30134)

* Removes redundant buffer zeroing

* Fix compile error
…xtual-type

[Property Wrappers] Use the outermost wrapper attribute type as the contextual type for property wrapper initialization
…empty-extensions

Revert "[PrintAsObjC] Don't include the module for empty extensions"
Tighten-up a Foundation Deserialization Test
@MaxDesiatov MaxDesiatov marked this pull request as ready for review April 14, 2020 17:19
@MaxDesiatov MaxDesiatov merged commit ce86f8e into swiftwasm Apr 14, 2020
@MaxDesiatov MaxDesiatov deleted the maxd/master-merge branch April 14, 2020 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.