Conversation

hot take #3: writing Rust would be easier if you could Just Use Rc when this is the case; in most contexts you can afford to do this, but Rust punishes you for it

Quote Tweet

Catherine

@whitequark

· Jan 19, 2018

Hot take #2: writing Rust can be hard sometimes because not all algorithms and designs naturally fit into its ownership model, and there's nothing wrong with either them or you. Gain some, lose some. twitter.com/TedMielczarek/

Ty Overby

@tyroverby

Jan 19, 2018

I feel this pain every time I want to prototype languages in Rust. Oh, you're trying to build an AST? If you use Box, Rc, or Arc, now all the goodness of pattern matching is gone.

Replying to

and

Totally feel this pain, as somebody who is devving on a language for work. Also the lack of recursion schemes is painful, and abstracting over pointer types. Also want to figure out a good port of Bound or Unbound for Rust 🤔

4:56 AM · Jan 22, 2018Twitter Web Client

Replying to

and

At times it makes me wonder if I should have just gone with Haskell or OCaml, and dealt with the toolchain issues later (I want nice cargo integration).