Mike J Innes
Mike J Innes
I agree. This just happens because of the way we expand things – ```julia ex = MacroTools.nothing b = MacroTools.nothing llama = (MacroTools.trymatch)($(Expr(:copyast, :($(QuoteNode(:(ex_ + b_)))))), ex) if llama ==...
Glad it's useful, thanks! You can fix this easily enough by adding `using MacroTools`, but it's pretty surprising that the above syntax doesn't import the MacroTools name into scope itself...
Yes, I think MacroTools is unlikely to add major new features at this point, and since some people clearly care about keeping dependencies few it would be fine to add...
I can see why this is confusing, but it's unavoidable; the `x_Markdown` is actually parsed as all one symbol and `@capture` parses it further.
Yeah, or perhaps by fixing the `rmlines` functions to do the same.
Not too trivial at all. It might be useful to have an `examples.jl` file or something with common patterns like this – feel free to open a PR for that.
I think I just left it out because I've always found `@capture` to be tons more useful. If you want to add a quick note on the syntax back in...
I think I'm a bit unclear on the purpose of this. Is the idea that with this patch you could more easily implement the `@kwdef` macro? Are there other use...
Right, so what benefit does this patch have, in that case?
Sorry, I see that the patch adds support for that syntax, but I still don't see what the use case or benefit is for that change. Since it's syntax that's...