home.social

#xmacro — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #xmacro, aggregated by home.social.

  1. @frankel and when strum is not enough there is the #xmacro crate (Note: I am its author) which has more flexibility at the cost of more verbose code.

    docs.rs/xmacro_lib/0.5.1/xmacr

    #rustlang

  2. @redfire @fasterthanlime
    Yes we are still at the beginning. #Unsynn should be good (but not complete) now when you don't need to parse #rust or it is OK for you to invest in boilerplate (see #xmacro).

    unsynn-rust is still unborn. It will take some time for a first release. Help and contributions will be greatly appreciated, but first when I am back from vacation I want to churn out some basics and guardrails how it should look like.

  3. @redfire @fasterthanlime
    Yes we are still at the beginning. #Unsynn should be good (but not complete) now when you don't need to parse #rust or it is OK for you to invest in boilerplate (see #xmacro).

    unsynn-rust is still unborn. It will take some time for a first release. Help and contributions will be greatly appreciated, but first when I am back from vacation I want to churn out some basics and guardrails how it should look like.

  4. @redfire @fasterthanlime
    Yes we are still at the beginning. #Unsynn should be good (but not complete) now when you don't need to parse #rust or it is OK for you to invest in boilerplate (see #xmacro).

    unsynn-rust is still unborn. It will take some time for a first release. Help and contributions will be greatly appreciated, but first when I am back from vacation I want to churn out some basics and guardrails how it should look like.

  5. @redfire @fasterthanlime
    Yes we are still at the beginning. #Unsynn should be good (but not complete) now when you don't need to parse #rust or it is OK for you to invest in boilerplate (see #xmacro).

    unsynn-rust is still unborn. It will take some time for a first release. Help and contributions will be greatly appreciated, but first when I am back from vacation I want to churn out some basics and guardrails how it should look like.

  6. @redfire @fasterthanlime
    Yes we are still at the beginning. #Unsynn should be good (but not complete) now when you don't need to parse #rust or it is OK for you to invest in boilerplate (see #xmacro).

    unsynn-rust is still unborn. It will take some time for a first release. Help and contributions will be greatly appreciated, but first when I am back from vacation I want to churn out some basics and guardrails how it should look like.

  7. @ajroach42 might #xdotool or #xmacro be useful? Record a macro of using the mouse to do it, and repeat that?
    e.g. xmacro.sourceforge.net/

    Could maybe even automate running the script by listening to udev?