Skip to content

Documentation: move the @_specialize discussion into proposals/UnsupportedOptimizationAttributes.rst #9786

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
May 19, 2017

Conversation

atrick
Copy link
Contributor

@atrick atrick commented May 19, 2017

proposals/UnsupportedOptimizationAttributes.rst.

proposals/UnsupportedOptimizationAttributes.rst.
@atrick atrick requested a review from swiftix May 19, 2017 20:01
@atrick
Copy link
Contributor Author

atrick commented May 19, 2017

@swiftix, once this is in, can you update the description to explain the current state of @_specialize, then decide if we should pick the docs changes onto 4.0?

@swiftix
Copy link
Contributor

swiftix commented May 19, 2017

@atrick Sure.

@swiftix swiftix changed the title Documentation: move the @_specialize discussion into Documentation: move the @_specialize discussion into proposals/UnsupportedOptimizationAttributes.rst May 19, 2017
@jrose-apple
Copy link
Contributor

Thanks, Andy!

@swiftix
Copy link
Contributor

swiftix commented May 19, 2017

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit 643d913 into swiftlang:master May 19, 2017
@swiftix
Copy link
Contributor

swiftix commented Jun 3, 2017

@atrick I added some documentation about @_specialize in #10095

@dabrahams
Copy link
Contributor

@swiftix …which I then had to revert. Did you ever get that straightened out?

@swiftix
Copy link
Contributor

swiftix commented Jun 4, 2017

@dabrahams You reverted the #10073. Afterwards I submitted and merged a fixed PR #10095

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.

5 participants