Tim Ryan

All of these seem to have some overlap in functionality, and it's confusing when to use which and what crate they live in.

I wrote this example for another project but think it would be useful to contribute to the examples/ folder. It's uses the Juniper library to implement a GraphQL server, and...

This project was instrumental in helping port over [parser-c](http://github.com/tcr/parser-c). I think there's a lot of potential in exploring what automated conversion from Haskell to Rust can do, given the similarities...

There are a few places in translated code in which /* Expr::Error */ is printed instead of whatever value it should have been. These should be diagnosed and cleaned up....

When a generator is encountered in code, we just output it as a `/* TODO: Generator */` comment. These are used a few times around the libraries we're porting so...

Similar to how top-level functions with multiple definitions are folded into a match statement (see the comment "There are multiple impls of this function, so expand this into a case...

This translates incorrectly. We should look at the type signature, and if there are extra arguments in its type that are not in the function arguments, it should be rewritten...

Translate fat arrow defns into "where" clauses.

1

e.g. ``` promote :: (Pretty node, Pos node) => node -> (Rust.Expr -> Rust.Expr -> Rust.Expr) -> Result -> Result -> EnvMonad s Result ```

e.g.: ``` 2 `infix` 2 ```

Obviously this isn't Rust's `return`, but it should do the right thing in monadic sequences.