Skip to content

[WIP] Nothing to see here...IUO changes. #14150

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

Closed
wants to merge 4 commits into from
Closed

[WIP] Nothing to see here...IUO changes. #14150

wants to merge 4 commits into from

Conversation

rudkx
Copy link
Contributor

@rudkx rudkx commented Jan 25, 2018

Just testing out some of the not-yet-merged IUO changes including some hacked up parameter matching code that will probably be rewritten.

rudkx added 4 commits January 24, 2018 16:56
…O attr on decl.""

This reverts commit c773493.

This was reverted from master when we added back some extensions to
ImplicitlyUnwrappedOptional<T>, but these changes are fine in a world
in which IUOs are implemented as Optional<T>.
…ObjectiveCBridgeable."

This reverts commit be6d83c.

We can remove these again since ImplicitlyUnwrappedOptional<T> is
going away.
Stop creating ImplicitlyUnwrappedOptional<T> so that we can remove it
from the type system.

Enable the code that generates disjunctions for Optional<T> and
rewrites expressions based on the original declared type being 'T!'.

This effectively means ImplicitlyUnwrappedOptional<T> is no longer
part of the type system, although I haven't actually removed all of
the code dealing with it yet.

Most of the changes supporting this were previously merged to master,
but some things, like support for dynamic lookup were difficult to put
on master without actually removing IUOs.

ImplicitlyUnwrappedOptional<T> is is dead, long live implicitly
unwrapped Optional<T>!

Resolves rdar://problem/33272674.
@rudkx
Copy link
Contributor Author

rudkx commented Jan 25, 2018

@swift-ci Please test

@rudkx
Copy link
Contributor Author

rudkx commented Jan 25, 2018

@swift-ci Please test source compatibility

@rudkx
Copy link
Contributor Author

rudkx commented Jan 25, 2018

Failures expected...

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - 4e48c40

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - 4e48c40

@rudkx
Copy link
Contributor Author

rudkx commented Jan 25, 2018

@swift-ci Please test

1 similar comment
@rudkx
Copy link
Contributor Author

rudkx commented Jan 25, 2018

@swift-ci Please test

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - 4e48c40

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - 4e48c40

@rudkx
Copy link
Contributor Author

rudkx commented Jan 25, 2018

In addition to the expected failure in ObjectMapper (which will be XFAILed by swiftlang/swift-source-compat-suite#127), it looks like SwiftLint is has a dependency on a version of SourceKitten that does not include jpsim/SourceKitten@8c92b0c, so it is also failing.

@rudkx
Copy link
Contributor Author

rudkx commented Jan 27, 2018

@swift-ci Please test Linux platform

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - 4e48c40

@rudkx rudkx closed this Jan 30, 2018
@rudkx rudkx deleted the test-current-param-code branch January 30, 2018 07:19
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.

2 participants