Skip to content

Rename canUnsafeCastValue to checkABIForUnsafeScalarCast and comment. #13805

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
Jan 8, 2018
Merged

Conversation

atrick
Copy link
Contributor

@atrick atrick commented Jan 8, 2018

This is an ABI-dependent routine, so at least should have ABI in the name. In
the future, the compiler may introduce new ABI layout rules for select types
based on the deployment target. Code like this needs to be reviewed at that time.

Clarify the comments.

@atrick
Copy link
Contributor Author

atrick commented Jan 8, 2018

@swift-ci smoke test and merge.

@gottesmm
Copy link
Contributor

gottesmm commented Jan 8, 2018

The new name makes it confusing to know when to do use this. Why not:

canPerformABICompatibleUnsafeCastValue or something like that. It reads better. That being said I don't care that much.

This is an ABI-dependent routine, so at least should have ABI in the name.  In
the future, the compiler may introduce new ABI layout rules for select types
based on the deployment target. Code like this needs to be reviewed at that time.

Clarify the comments.
@atrick
Copy link
Contributor Author

atrick commented Jan 8, 2018

@swift-ci smoke test and merge.

2 similar comments
@gottesmm
Copy link
Contributor

gottesmm commented Jan 8, 2018

@swift-ci smoke test and merge.

@gottesmm
Copy link
Contributor

gottesmm commented Jan 8, 2018

@swift-ci smoke test and merge.

@swift-ci swift-ci merged commit 300d261 into swiftlang:master Jan 8, 2018
@atrick atrick deleted the comment branch May 9, 2018 23:51
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