Skip to content

[test] Verify that TypeDecoder handles same-type constraints properly #26045

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 1 commit into from
Jul 24, 2019

Conversation

jrose-apple
Copy link
Contributor

Follow-up for #25984 recommended by Slava. (RemoteAST is next but that might actually have problems…or I might be holding it wrong.)

@jrose-apple jrose-apple requested a review from slavapestov July 9, 2019 23:56
@jrose-apple
Copy link
Contributor Author

@swift-ci Please test

// CHECK-TYPE: STSContainer℠<STSOuter>.Subclass2<Int>

// DEMANGLE-TYPE: $s13nominal_types12STSContainerO9Subclass3CyAA8STSOuterV_SiG
// CHECK-TYPE: STSContainer<STSOuter>.Subclass3<Int>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops. This one has a constraint on it and I'm not passing a valid argument. It's working by coincidence because I wrote the wrong mangled name.

@jrose-apple
Copy link
Contributor Author

@swift-ci Please smoke test

@jrose-apple
Copy link
Contributor Author

@swift-ci Please smoke test Linux

@jrose-apple
Copy link
Contributor Author

@slavapestov Ping. I think there's no downside to taking these tests, even if we have to leave the Remote* ones for later?

@jrose-apple jrose-apple merged commit 1586105 into swiftlang:master Jul 24, 2019
@jrose-apple jrose-apple deleted the merry branch July 24, 2019 15:56
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