Alec Theriault

Well I still think the increased memory usage is still probably due to us loading more interfaces than before. I'm not sure what clever tricks we can do to fix...

Here is the GHC 8.6.1-alpha2 producing Haddocks for the `ghc` library (with `+RTS -pa -hc -RTS`): And here it is with deddced31cabadf62fe01fff77b094cd005e52a1 reverted: Given such a drastic difference, it looks...

Some progress is happening in https://gitlab.haskell.org/ghc/ghc/-/merge_requests/6224. That patch should mean that Haddock doesn't need to use the GHC plugin interface anymore, which hopefully should reduce the amount of memory used...

It might be worth looking at what GHC has done: they're in a somewhat similar position of having limited resources but aspiring to check as many configurations as possible. *...

Might be worth considering an `Invalid` constructor given the number of times Rust relies on that idea. Either that, or adjust the AST to get rid of this pattern (and...

For now, `Ident` stayed the same, and instead the AST was adjusted to avoid having to fill `Ident` holes with an empty/filler/invalid `Ident`. Still not ruling out the possibility of...

Reopening this for the more general problem of how to efficiently deal with `Ident` and `Name`.

[This commit](https://github.com/harpocrates/language-rust/commit/6b15d8ad3d20c6754fb5f3833946a1a6eb36db76) removed the `Name` data type and just changed it to be a synonym for `String`. After a couple more simplifications, things ended up pretty nice. This issue is...

There are really two ideas to keep track of here: 1. Compacting common `Name`'s ([like the previous comment](https://github.com/harpocrates/language-rust/issues/3#issuecomment-286653841)) 2. Representing `Name`'s in a format that saves bytes and pointer indirection...

Here is a simple example of why we need the `ViewPatterns` approach: ``` > let x = [expr| 1 |] > let y = [stmt| $x; |] :42:9: error: •...