Lukas Kalbertodt

~~I hand optimized the non-trig version by replacing all `powf()` calls with repeated multiplication in #30 (luckily the only powers we raise to are 2, 4, 6 and 8). Turns...

Out of curiosity: what's your use case for this conversion? Thinking about it, I wonder if it makes sense to implement `quote::ToTokens` instead? But yeah, I guess re-parsing it is...

I took a look at this issue again. I decided against `quote::ToTokens` as `litrs` does not depend on `quote` yet. However, i added the following things: - `raw_input` and `into_raw_input`...

@wycats Did you get a chance to look at my changes? Any comments? If you don't have the time or lost interest in this, that's totally fine, of course!

Yes, in principle I want `litrs` to exactly accept what the Rust compiler accepts. I don't want any grammar difference. However, (a) `proc_macro2` is an external crate so there can...

I assume you are talking about `TryFrom for Y` where `Y` is `litrs::StringLit`, `litrs::IntegerLit` and so on? That's a great idea! What could X be then? `proc_macro[2]::Literal` for sure. But...

Yeah `TokenTree` also makes sense. Sweet, thanks.

@jhpratt I just published 0.2.0 which contains a large number of `From` and `TryFrom` impls. It was actually more work than expected, but I think they really improve the library...

I would also welcome this API addition. Though I would probably rather call it `parse_header_value` or something like that. Having another API for parsing from a `&http::HeaderValue` would also be...

That, of course, sounds like a much better solution! And it's good to know that many outlier warnings are in fact not very meaningful (I already felt like a criminal...