Alexander Regueiro
Alexander Regueiro
Right. You’d probably want a keyword after enum members too in that case… but having no keyword for anything might be fine. > On 6 Jul 2016, at 22:42, Paul...
By the way, generic enum types aren't currently supported, are they?
I talked with some people on IRC about this, and it seems that an imperfect implementation is doable at least. Could we at least aim for a “bad” temporary solution?...
I am, yes. And sorry to sidetrack. Maybe I’ll have a go, but the current code is basically magic heh. Perhaps a syntax extension/custom derive is the way to go...
Even basic support for generics would be of enormous benefit to me... is there any chance we could get this working? I tried fiddling with the code, but it's truly...
@tailhook Are you aware of https://danielkeep.github.io/rust-parse-generics/doc/parse_macros/ ? This may make the job of adding support for generics a lot easier. And right now, I'd pay for generics support! :)
Not sure, but I believe so. I got pointed to this by someone on IRC. Here’s the GitHub: https://github.com/DanielKeep/rust-parse-generics Let me know what you think. > On 10 Jul 2016,...
Yep. An abstract rendering API might take a bit more thought than simply refactoring, but I am all for this!
What do you mean by a "normal string"?
It would be nice, yep, but let's keep it in separate packages/modules as @ForNeVeR suggests.