Skip to content

SILGen: disambiguate apply overload #24276

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
Apr 25, 2019

Conversation

compnerd
Copy link
Member

The anonymous universal initialiser would result in ambiguous selection
of the constructor. Name the type being constructed.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

The anonymous universal initialiser would result in ambiguous selection
of the constructor.  Name the type being constructed.
@compnerd
Copy link
Member Author

CC: @slavapestov

@compnerd
Copy link
Member Author

@swift-ci please smoke test and merge

@slavapestov
Copy link
Contributor

Fair enough. I'd prefer SubstitutionMap() but its no big deal

@compnerd
Copy link
Member Author

compnerd commented Apr 25, 2019

I can change them in a follow up. Want to get things repaired first. This is the third break in the last 16 hours.

@swift-ci swift-ci merged commit 4fa916b into swiftlang:master Apr 25, 2019
@slavapestov
Copy link
Contributor

@compnerd I'm changing it in #24267

@compnerd compnerd deleted the strike-three-and-youre-out branch April 25, 2019 22:47
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.

3 participants