Remon is a responsible library developer. She cares about stability, flexibility and correctness, using whichever tools are presently accessible to achieve those goals. Her authored libraries feature automated testing and extensive documentation; she allots design decisions rationale; she knows her language features and traditions and how to apply them to best effect.

A short post on how variable names can leak out of macros if there is a name collision with a constant. I thought this was a delightful read!

  • livingcoder
    7·
    2 months ago

    This was a great post, but is the last state of the macro actually bad for performance in any way? I get that it’s ugly (and we should only choose to make code less readable like this when there’s actually an issue) but is it worse for runtime performance?

    • TehPers@beehaw.orgEnglish
      9·
      2 months ago

      Adding a single unused function should no effect on runtime performance. The compiler removes dead code during compilation, and there’s no concept at runtime anyway of “creating a function” since it’s just a compile-time construct to group reusable code (generally speaking - yes the pedants will be right when they say functions appear in the compiled output, to some extent).

      Anyway, this can all be tested on Godbolt anyway if you want to verify yourself. Make a function with and without a nested unused function and check the output.

    • arendjr
      2·
      2 months ago

      Runtime performance is entirely unaffected by the use of macros. It can have a negative impact on compile-time performance though, if you overdo it.

      • livingcoder
        3·
        2 months ago

        I understand that the macro only affects compile time but I’m talking about the extra function that’s included in the resulting source code when the macro is expanded during compile. Based on other feedback, it looks like the unused function is optimized away.

  • BB_C
    310·
    2 months ago

    Maybe a good idea for a post. But the amount of reaches required makes this icky.

    • Pretending people write:
      let Ok(x) = read_input() else { return Err(Error) };
      instead of
       let x = read_input().map_err(|_| ...)?;
    • Pretending people write:
       const x: &str = "...";
      instead of
       const X: &str = "...";
    • Pretending there exist people who have such knowledge of rust macros hygiene, ident namespaces, etc, but somehow don’t know about how macro code expands (the “shock” about the compile error).

    Maybe there is a reason after all why almost no one (maybe no one, period) was ever in that situation.

    • BB_C
      102·
      2 months ago

      Also:

      A short post on how variable names can leak out of macros

      I don’t think you understood the blog OP!