Jacob Pratt
Jacob Pratt
So it turns out this is going to be a fair bit more complicated than I had hoped. `` tags for marking the code as a given language, inside a...
Having some sort of macro would be ideal. I'm not sure it's possible to implement in a `macro_rules!`, unfortunately.
How could it be implemented as a function? Unless you're taking dyn args, you'd have to accept a Vec (which would restrict types) to allow for an arbitrary number of...
I'll definitely take a look to attempt to understand how that works, but it certainly looks promising. Maybe someday I'll be able to write complex `macro_rules!` like that myself. @seanmonstar...
I've just simplified the macro provided by @SafariMonkey. It only has four rules, two of which are internal. While likely having near zero impact on the actual performance, I've changed...
Of course documentation isn't present in the sample — I still hardly understand how the macro works. I basically just spent a little time hacking away to inline the splitting...
@CryZe messaged me yesterday about this, actually. He's working on a PR that would do this in a backwards-compatible way.
The primary problem that formatting into `fmt::Write` is that arbitrary bytes can be present in the format description. It's not immediately clear how this interacts with an output that requires...
It has to be under a different method name. Feature gates can't change a method signature.