Then we'll need to consider how these are transformed through the network. For other layers, we could consider adding an option to specify output features as keywords:
I am not sure I like the mixing of keyword lists vs tuples - in a way I would prefer a separate :names option, as in Nx, but maybe we should be allowing keyword lists in Nx too....
On the high-level API, we can integrate named tensors by specifying the expected names on input:
Then we'll need to consider how these are transformed through the network. For other layers, we could consider adding an option to specify output features as keywords: