Alec Theriault
Alec Theriault
@jgm @alexbiehl @gbaz This is following up the discussion in https://github.com/haskell/haddock/pull/729. I'm opening a new issue despite https://github.com/haskell/haddock/issues/244 and https://github.com/haskell/haddock/issues/570 because I'd like to focus on the particular issues around...
Add support for all of the newest Rust features. These include - async blocks, async closures, async functions - try blocks - await - or-patterns - associated type constraints -...
The following sorts of things should parse: ```rust trait Foo { type Bar
The following should parse, but it doesn't currently: ```rust pub unsafe extern "C" fn test(_: i32, ap: ...) { } pub unsafe extern "C" fn test_valist_forward(n: u64, mut ap: ...)...
The following test case (taken from `rustc`'s testsuite) doesn't parse: ``` // build-pass (FIXME(62277): could be check-pass?) #![allow(bare_trait_objects)] type A = Box u8) + 'static + Send + Sync>; //...
It is expected that the following will be valid macro definitions: ```rust macro foo($a: ident) => { return $a + 1; } ``` ```rust pub macro foo { ... }...
Rust supports two syntaxes for `mod` - one for declaring inline a module and another for referencing the contents of another file. We don't currently try to go follow those...
The rust AST has special forms for inline and global assembly. It might be worth adding explicit support for these. This is not urgent since both inline and global assembly...
Consider adding benchmarks to check memory-use and speed of the pretty-printer.
It may be the case that identifiers or names should be interned, or use `Text`, but in any case the current situation should change.