Michelle Casbon

It looks like [this line](https://github.com/tensorflow/swift-apis/blob/master/Sources/TensorFlow/Core/Tensor.swift#L771) is always returning the CPU device. I'll figure out how to surface the actual device being used.

Once [swift-apis#1156](https://github.com/tensorflow/swift-apis/pull/1156) is merged, `TFE_TensorHandleDeviceType` and `TFE_TensorHandleDeviceID` will be available, making this a straightforward fix.

Tentative changes [here](https://github.com/tensorflow/swift-apis/compare/main...texasmichelle:eager_device).

I ran into a problem adding [eager/c_api_experimental.h](https://github.com/tensorflow/tensorflow/blob/v2.4.0/tensorflow/c/eager/c_api_experimental.h#L446) since it contains C++ syntax in the initialization of the `TFE_CustomDevice` struct. ``` /home/michellecasbon/repos/out/libtensorflow-prefix/src/libtensorflow/tensorflow/c/eager/c_api_experimental.h:446:14: error: expected ';' at end of declaration list int...

I expected this to be possible by conforming the associated types for `RecurrentLayerCell` to `DifferentiableTensorProtocol`: ``` public protocol RecurrentLayerCell: Layer where Input == RNNCellInput, Output == RNNCellOutput { associatedtype TimeStepInput:...

@brettkoonce Can you share what you're seeing? I'm getting a warning about disk size, but otherwise that command seems to be working. Are you running in a project that has...

Or are you pointing this out as an example of a toolchain running with cuda 11 support?

ah, I see what you mean. I also tried using `--image-family=swift-latest-cu110-ubuntu-1804`, which seems fine on the `tensorflow-0.12` branch of swift-models. However, I can see that the 0.12 release hasn't made...

@brettkoonce You can expect to see DLVMs with v0.12 right after the freeze, e.g. by Jan. 8. I also verified that cuda 11.0 is included in the existing toolchain and...

as @shabalind pointed out, similar to `brew doctor` 👍