Replace beer
example with expanded alchemy
example
#262
Labels
documentation
Improvements or additions to documentation
beer
example with expanded alchemy
example
#262
Not a blocker for open-source alpha.
In my opinion, the beer example is a bit simplistic. We should strive to include all features as examples in this dialect. Sure, we target compiler developers that "know" how MLIR works but unless we are exactly following previous precedent (and citing it everywhere!) users will still need to understand the particular structure of how we write code. Thus, the "cookbook" should be complete to give precedent to those prospective users.
I brought this up a few weeks ago, but an "alchemy" dialect might be appropriate as it can act as a simulacrum of quantum circuit execution and orchestrating external computations. We could even have a "magic state distillation" example haha. It can also act as a way to demonstrate rewrite passes by having a high level and low level dialect group.
For example, the high level dialect could be instantiating reagents (eye of neut, toe of frog or whatever), mixing them together (with possibly random results, there is that rewrite!) in ways that require real-time control flow and unknown types (abstract analysis and type lattice!) to generate potions or whatever. Then the low level dialect (rewrite!) could be allocating beakers and vials (atoms/qubits?!) and executing things on the register level (atom moves?!).
The text was updated successfully, but these errors were encountered: