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.

Sign up for GitHub

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

Jump to bottom

Moving to Swift #18

Open

mortendahl opened this issue Feb 10, 2020 · 0 comments

Member

mortendahl commented Feb 10, 2020 •

edited

Loading

Explore to what extent it makes sense to move (parts of) the TFE codebase Swift, and if so, outline what this would look like.

Pros:

strong typing system
better integration of custom kernels/MLIR

Cons:

performance seems to be worse in S4TF (at the current stage): S4TF speed tensorflow/swift-apis#630

Questions:

is S4TF suitable for (expressing) distributed computations?
how would S4TF fit together with TFE compiler and runtime?
how easy is it to use Swift code from Python, or would it require users moving to Swift as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment