Nick Cameron
Nick Cameron
I've started some editing this week. I intend to work on this some more over the next week or so.
cool, sounds like an interesting project. Feel free to ping me on irc if you need any help/info.
`proc_macro_hygiene` is now the only feature being used.
It looks like we can't use proc-macro-hack because we want to introduce variables into the calling context, which requires a statement-level expansion, not an expression level one (because of the...
I just pushed a commit which adds the expression form. It always returns a tuple of results, which is not great for single values, but that should be fairly easy...
it should
We could allow an empty format string in the statement form too: `scanln!(x: i32)` is equivalent to `scanln!("{}", x: i32)`
> I came to the same conclusion after several months of using Single values are not tuple-wrapped now
Could the constructor always be `const`? I think that anything we generate should be `const`-able? Maybe with the more complicated options we would have to make them not `const` to...
> Oh, bigger issue: Default::default is (unsurprisingly) not a const fn. So presumably a lot of uses of this crate break it it were always const. Why is this an...