Stephen Sugden

It appears that `fn render(state: &State) -> impl DomNode` doesn't work? Here is a small example program: ``` #![feature(conservative_impl_trait)] extern crate domafic; #[cfg(not(target_os = "emscripten"))] fn main() { panic!("This example...

thank you, that does make this example compile :smile:. Now to figure out what I'm doing wrong in my actual program.

similar to what I suggested on issue #2, I think the docspec should refrain from defining textual formats as much as possible. I think the choice of files as the...

The names are still unique, they are just organized into a hierarchy instead of a flat mapping. I don't think the speed difference in lookups is worth worrying about, and...

Why not have the namespace be a JSON list? That way transformers and formatters don't need to parse an arbitrary text string. edit: After looking at the spec, I see...

The only doctool I really know anything about is Sphinx, and it definitely uses an in memory abstraction of the documented code. It's capable enough to create all the Python...

@Maher4Ever just ran into the same thing, please merge.

I would also like to see a diff or more detailed information about why prettier thinks a file isn't formatted. I currently don't run `prettier --check` in CI/pre-commit hooks because...

As I said in my first message. I have already run prettier on those files, but it still shows the warning. Trying to make a more useful error report is...

so here's what I just did, all locally, no CI involved. ``` $ yarn prettier --check some-file.ts yarn run v1.22.4 $ prettier --check some-file.ts Checking formatting... [warn] path/to/some/file.ts [warn] Code...