Skip to content

Community Feedback #1

Description

@LukasKalbertodt

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.

Activity

  1. jhpratt commented on May 25, 2021

    @jhpratt

    I haven't had a chance to test this out yet, but I think having TryFrom impls could be quite convenient. It would avoid the match with a single type expected with the rest panicking (.expect could be used or some other error handling).

  2. LukasKalbertodt commented on May 25, 2021

    @LukasKalbertodt
    OwnerAuthor

    I assume you are talking about TryFrom<X> 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 also String and &str? Probably all four options, right?

    EDIT: no, I wasn't thinking straight. The &str and String cases are already covered by parse, of course. But yeah, for the proc_macro[2]::Literal types it makes perfect sense!

  3. jhpratt commented on May 25, 2021

    @jhpratt

    I was imagining proc_macro::Literal and proc_macro::TokenTree (along with proc_macro2 equivalents).

  4. LukasKalbertodt commented on May 25, 2021

    @LukasKalbertodt
    OwnerAuthor

    Yeah TokenTree also makes sense. Sweet, thanks.

  5. LukasKalbertodt commented on May 28, 2021

    @LukasKalbertodt
    OwnerAuthor

    @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 and make lots of real world uses cases easier. Thanks for the suggestion again!

  6. wycats commented on Oct 2, 2021

    @wycats

    @LukasKalbertodt I stumbled across this crate and really love it. Thank you so much for doing this!

  7. xiyuzhai commented on Dec 26, 2022

    @xiyuzhai

    I'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!!!

  8. LukasKalbertodt commented on Oct 20, 2025

    @LukasKalbertodt
    OwnerAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions