Repository navigation
Community Feedback #1
Description
Activity
I haven't had a chance to test this out yet, but I think having
TryFromimpls could be quite convenient. It would avoid thematchwith a single type expected with the rest panicking (.expectcould be used or some other error handling).I assume you are talking about
TryFrom<X> for YwhereYislitrs::StringLit,litrs::IntegerLitand so on? That's a great idea! What could X be then?proc_macro[2]::Literalfor sure. But alsoStringand&str? Probably all four options, right?EDIT: no, I wasn't thinking straight. The
&strandStringcases are already covered byparse, of course. But yeah, for theproc_macro[2]::Literaltypes it makes perfect sense!I was imagining
proc_macro::Literalandproc_macro::TokenTree(along withproc_macro2equivalents).Yeah
TokenTreealso makes sense. Sweet, thanks.@jhpratt I just published 0.2.0 which contains a large number of
FromandTryFromimpls. It was actually more work than expected, but I think they really improve the library and make lots of real world uses cases easier. Thanks for the suggestion again!Reacted by Jacob Pratt@LukasKalbertodt I stumbled across this crate and really love it. Thank you so much for doing this!
Reacted by Lukas KalbertodtI'm working on my own programming language https://github.com/xiyuzhai-husky-lang/husky/. I shall work out the literal part of my language based on this project. Amazing work!!!
Thanks again for your feedback! I just released v1.0 and will close this open ended issue. Of course, feedback is still appreciated as separate issues, for example.
Do you have any opinions, complaints, suggestions, ideas, ... about
litrs? Let me know! This issue is less formal and more relaxed than "normal issues", so feel free to just dump your thoughts here.