Generalization of Implicit Conversions #1431
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@johnno1962 I think the conversation in the thread this originated in moved on since – should this be closed for now while further discussion continues? |
|
How-so? There haven't been any posts on any of the threads this originated from since I opened this - Perhaps that's more the issue. It takes quite a lot of time to try to float a proposal from outside Apple including preparing and benchmarking an implementation. What would be the pressing need closing this out at this stage would serve? |
rjmccall
added
the
LSG
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Apple,
I'm submitting this now as in a sense it has been thrashed out on the forums a number of times. If I were to summarise the sentiment I've seen when it comes to proposing a mechanism for "custom implicit conversions" people have a problem with both of the words "custom" and "implicit" in the community. I view this as a shame as I feel this could be a useful addition to the Swift compiler's superpowers without being particularly difficult to understand or "dangerous"; Its main critique being it could be too powerful for many people's taste. The implementation is a bit sketchy but is only intend as a proof of concept that such a feature can be introduced without slowing down type checking. See the comments in the original PR from May.
Cheers,
John