This repository was archived by the owner on Mar 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 610
v0.3 release. #175
Merged
Merged
v0.3 release. #175
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
f87bfc7
v0.3 release.
dan-zheng 751a77d
Address feedback.
dan-zheng dde0bbf
add links to new release
1aa9468
fix install URL
6a02acd
Address feedback.
dan-zheng 838a8eb
fixes to Installation.md
810ea5d
Merge branch '0.3' of github.com:dan-zheng/tensorflow-swift into 0.3
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,96 @@ | ||
| # Swift for TensorFlow Known Issues | ||
|
|
||
| This is a curated list of known Swift for TensorFlow issues. With every release, | ||
| new issues are added and resolved issues are updated. | ||
|
|
||
| Please see the [JIRA issue tracker](https://bugs.swift.org/projects/TF/issues) | ||
| for a full list of known issues. | ||
|
|
||
| ## Version 0.3 | ||
|
|
||
| ### TensorFlow Library | ||
|
|
||
| * [ ] `Tensor` advanced indexing and striding are not supported on GPU. | ||
|
|
||
| ## Version 0.2 | ||
|
|
||
| ### Notebook Environments (Colab and Jupyter) | ||
|
|
||
| * [ ] When a runtime error occurs or when you interrupt cell execution, | ||
| resources (e.g. host memory, GPU memory) do not get released. This can | ||
| lead to OOMs. ([TF-338](https://bugs.swift.org/browse/TF-338)) | ||
| * Workaround: Restart the runtime (`Runtime > Restart Runtime` in the Colab | ||
| menu bar) to release all the resources. | ||
| * [ ] If the last statement on a cell evaluates to a struct that was defined in | ||
| the notebook, then you get an error ("use of undeclared type") instead of | ||
| seeing the value of the statement. | ||
| ([TF-125](https://bugs.swift.org/browse/TF-125)) | ||
| * Workaround: Wrap the last statement in `print()`. | ||
| * [ ] Using extensions to conform a type to a protocol (e.g. `extension MyType: | ||
| MyProtocol { ... }`), often causes duplicate conformance errors. | ||
| ([TF-162](https://bugs.swift.org/browse/TF-162)) | ||
| * Workaround: Add the conformance in the same cell where the type is defined. | ||
| * [ ] If a cell that declares a type executes twice, then it creates two | ||
| different types with the same name. Mixing these types can lead to | ||
| confusing error messages like `cannot convert value of type 'MyType' to | ||
| expected argument type 'MyType'`. | ||
| ([TF-156](https://bugs.swift.org/browse/TF-156)) | ||
dan-zheng marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| * Workaround: Re-run all cells that use the declared type, so that they use the | ||
| new type. | ||
| * [ ] The autocomplete UI should show types and documentation. It should | ||
| position your cursor in the first argument when you complete a function | ||
| call. | ||
|
|
||
| ### Swift Standard Library Enhancements | ||
|
|
||
| * [ ] The | ||
| [`Differentiable`](https://www.tensorflow.org/swift/api_docs/Protocols/Differentiable) | ||
| protocol's `allDifferentiableVariables` requirement should not have a | ||
| setter. Do not use this directly through a generic type with a | ||
| `Differentiable` conformance constraint. | ||
| ([TF-208](https://bugs.swift.org/browse/TF-208)) | ||
|
|
||
| ### Swift for TensorFlow Deep Learning Library | ||
|
|
||
| * [ ] Many Keras layers remain to be implemented, help wanted! | ||
| ([swift-apis#54](https://github.com/tensorflow/swift-apis/issues/54)) | ||
| * [ ] There is no built-in API for parameter sharing. | ||
| * [ ] The | ||
| [`Parameter`](https://www.tensorflow.org/swift/api_docs/Classes/Parameter) | ||
| class does not conform to `Differentiable` yet, and is not recommended for | ||
| general use. | ||
| * [ ] The compiler errors displayed when a user-defined layer struct fails to | ||
| fully satisfy the requirements of the `Layer` protocol are unclear. | ||
|
|
||
| ### Automatic Differentiation | ||
|
|
||
| * [ ] Differentiation does not yet support functions with control flow. | ||
| ([TF-356](https://bugs.swift.org/browse/TF-356)) | ||
| * [ ] Differentiating functions with respect to an `inout` parameter is not yet | ||
dan-zheng marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| supported. ([TF-357](https://bugs.swift.org/browse/TF-357)) | ||
| * [ ] The compiler will only synthesize conformance requirements for | ||
| `Differentiable` in `struct` types. | ||
| ([TF-37](https://bugs.swift.org/browse/TF-37)) | ||
| * [ ] The `@differentiable` attribute incorrectly passes type-checking in some | ||
| cases, when an error should be produced. This leads to compiler crashes. | ||
| ([TF-449](https://bugs.swift.org/browse/TF-449)) | ||
| * [x] ~~The `@differentiating` attribute leads to a compiler crash when the | ||
| derivative function is defined in a generic context that is more | ||
| constrained than the original function's generic context. | ||
| ([TF-358](https://bugs.swift.org/browse/TF-358))~~ | ||
| * Resolved (v0.3). The `@differentiating` attribute can register derivatives | ||
| with a generic context that is more constrained than the original function's | ||
| generic context. | ||
| * [ ] Referring to a `@differentiable` function using key paths leads to a | ||
| compiler crash. ([TF-123](https://bugs.swift.org/browse/TF-123)) | ||
|
|
||
| ### Python Interoperability | ||
|
|
||
| * [ ] When the execution of a Python expression raises an exception, the stack | ||
| trace will not show the Python call stack. | ||
| * [ ] When an argument to a Python function cannot be converted to a Python | ||
| object, the compiler wrongly claims that the function is of non-function | ||
| type rather than pointing out that the argument doesn't conform to | ||
| `PythonConvertible` ([TF-220](https://bugs.swift.org/browse/TF-220)). | ||
| * [ ] Python TensorFlow cannot be imported because of various issues (binary | ||
| incompatibility, symbol conflicts). | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there an API link?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are actually supported. What's not supported on GPU are the subscript setters only (i.e., assignment).