Yusuke Oda

Some features are taken over by other issues. Closes this issue for now.

All are now supported. Since it is hard to disambiguate set/bit operations, it is now controlled by a flag.

I have some ideas about this. - First, we can provide the `ExpressionCodegen`, which converts `ast.expr` to LaTeX. I think `ast.expr` is the minimal fragment of AST that we can...

> ExpressionCodegen(ast.NodeVisitor) would be the parent class to FunctionCodegen, AlgorithmCodegen, etc We don't need inheritance (and shouldn't adopt inheritance here IMO) because there's basically no advantage over composition in this...

I guess you meant some argument to specify the output style. Yes we need to have one for it (and maybe it'd be better to integrate the current `function` and...

Yes. And we should have functions for every choice of style. As this is an essential config, users shouldn't write the style parameter every time.

I don't like the image approach actually, so going with two codegens is fine. > `~~~~` Better to use `\hspace{width}` rather than whitespace characters, because indentation does not mean anything...

This should be an additional features of #81.

@erica-w-fu Hi, feel free to work on this! Since the overall syntax around Match is very huge, I'd like to decompose it to small developments (pull requests) mainly for ease...

Basically implementing some codegen rules in `function_codegen.py` is all you need. As for "small development", you can start to implement only a specific portion in the whole syntax (e.g., I...