Skip to content
This repository has been archived by the owner on Jul 1, 2023. It is now read-only.

[Layer] 'func call' -> 'func callAsFunction'. #172

Merged
merged 1 commit into from
Jun 4, 2019
Merged

Conversation

rxwei
Copy link
Contributor

@rxwei rxwei commented Jun 4, 2019

Apply the final naming decision in SE-0253 to the TensorFlow library. This depends on apple/swift#25235.

Shall be merged in time for the Swift for TensorFlow 0.4 release.

@rxwei rxwei requested a review from dan-zheng June 4, 2019 05:14
@rxwei rxwei changed the title [Callable] 'func call' -> 'func callAsFunction'. [Layer] 'func call' -> 'func callAsFunction'. Jun 4, 2019
…/swift-evolution/blob/master/proposals/0253-callable.md) to the TensorFlow library. This depends on [swiftlang/swift#25235](swiftlang/swift#25235).

Shall be merged in time for the Swift for TensorFlow 0.4 release.
@rxwei rxwei merged commit e909225 into master Jun 4, 2019
@rxwei rxwei deleted the callAsFunction branch June 4, 2019 07:00
@pschuh
Copy link
Contributor

pschuh commented Jun 4, 2019

I think we're approaching the point where changes like this should compile before and after the breaking compiler change.

@rxwei
Copy link
Contributor Author

rxwei commented Jun 4, 2019

How would you make that work? This depends on a compiler change, but a toolchain with the new changes cannot be built without this change. It's a circular dependency.

@pschuh
Copy link
Contributor

pschuh commented Jun 4, 2019

Here are some approaches:
If the feature is orthogonal (a rename), make both names work.
A more general approach that will always work is to protect with a flag inside the compiler or a flag in the swift-apis repo.

@rxwei
Copy link
Contributor Author

rxwei commented Jun 4, 2019

Sounds good.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants