lolbinarycat

@fmease That's a very good point, it would be nice to have some syntax that encapsulates both. Perhaps a syntax like `doc(nomalize::consts = ...)` and `doc(normalize::types = ...)` ? it...

@fmease added a `normalize::` prefix, what do you think about that?

these should probably be associated functions, not methods. also, this seems to ignore another type of pointer tagging, often used by interpreters, where the bottom bits (otherwise always zero because...

> For many years you could write `(x: Type)` in a pattern on nightly. I think that was never implemented fully and ended up being removed but sounds like this...

having an array of generators, including those provided by other crates.

@vassudanagunta ah, I see the error now. I'm not used to grammars that require infinite lookahead. The following *is* a code span: ~~~ 5 ``` 555 ``` ~~~ still, I...

[here is the documentation i am confused about](https://github.com/drahnr/cargo-spellcheck/blob/master/docs/configuration.md#format) is the dictionary relative to Cargo.toml or the config.toml of cargo-spellcheck? DICPATH is used in hunspell itself, although i'm not sure if...

I want to link *from the definition of builtin macros* to a page explaining what builtin macros are. If we want to ignore the existence of `no_core`, we could say...

That section only mentions built-in *attributes* as far as i can tell, the built-in function-like macros are not mentioned as being part of *any* prelude, aside from the fact that...

@GuillaumeGomez the `windows` crate will not see any size increase (beyond the 6 bytes of the empty u field), as it does not use thr staged_api feature, and we only...