-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Remove -enable-experimental-nested-generic-types flag #5600
Remove -enable-experimental-nested-generic-types flag #5600
Conversation
6ed9cd9
to
0bca680
Compare
Fantastic! |
-1 ABI FIXMEs in the standard library is a good day |
3c7bf25
to
0ee99c8
Compare
Almost works! Hitting a weird generic metadata cache bug now, interesting... |
aa64b6a
to
c71652b
Compare
Build failed |
Build failed |
c71652b
to
b4f55f7
Compare
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
Build failed |
Build failed |
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
Build failed |
FYI, I dealt with the compiler_crashers failure separately. The |
…ata() Previously we had two separate mechanisms to turn a metatype into a string. The swift_typeName() function was used to print the metatype in a human-readable fashion, whereas the _swift_buildDemanglingForMetadata() was used when naming generated generic Objective-C classes. Unify them, since what swift_typeName() does is redundant; instead of going directly from the metatype to a human-readable string, we can get the mangling, and print that using the demangler. This fixes some issues with unnecessary parenthesis when printing function types, and also allows Objective-C classes to be instantiated with nested generic types as parameters.
…nd Dictionary Resolves ABI FIXME swiftlang#34 and <rdar://problem/17002096>.
I don't know what the 'CHECK-NOT: extension [' line means, but now we have a nested type inside Dictionary.
The swift-api-digester doesn't know about generic typealiases (yet?). So it picks up some changes that are not actually source-breaking from the previous patch.
b4f55f7
to
7ba5617
Compare
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
Build failed |
Build failed |
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
Build failed |
914c0bc
to
b3bc749
Compare
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
|
||
extension OuterNonGeneric.InnerGeneric {} | ||
extension OuterGeneric.InnerNonGeneric {} | ||
extension OuterGeneric.InnerGeneric {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I constrain the outer generic parameter? (if it has a different name)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep
w00t! |
Looks like this means we can also tackle FIXME #23 ( |
rdar://problem/18869049
rdar://problem/17002096