(Found this while reviewing #907)

Currently Expr::operator=(const Expr &o) can have two meanings.

https://github.com/taichi-dev/taichi/blob/f5373b1395a66c78506de0fd3c172dffe0d444d0/taichi/ir/expr.cpp#L54-L69

Let's say we have

Expr a, b;
a = b;

1. If inside a kernel definition, this creates a FrontendAssignStmt in the AST
2. Otherwise, this lets a hold the express

The default issue template suggests that all Swift for TensorFlow issues should filed on bugs.swift.org:

We are using JIRA instead of GitHub issues to track
our work in order to integrate more effectively with the rest of the Swift
ecosystem.

Ankit Shah and I are trying to use Gen to support a project and would love the addition of a dirichlet distribution

Now that we support a multitude of basic layers, I'd like this issue to serve as the discussion for supporting advanced layers. While #54 tracked basic layers and most have been implemented, We now need to consider which of the following to add in swift-apis. tensorflow/swift-models#231 added bert, with that also added support for transformers and attention layers. Having reviewed a variety of cur

I'm curious if your visions include making it a feature-complete NN training framework?

What will be the master plan? Integrating with Torch/TF/MXNet or build hardware-level compilation framework from scratch?

Also, what is the standard & code of conduct for contributions from the community?

I'm totally convinced of its capability and believe it can fit into the missing link between horiz