I feel like I have seen this proposal before, but I can’t find it now and I don’t remember the resolution, so sorry if this is repetitive. I think it would be very nice if single word arguments passed to a function after a semi-colon were interpreted as keyword arguments where the variable name is …

This is implemented in the language itself, since v1.5: add implicit named tuple and keyword argument names JuliaLang:master ← JuliaLang:jb/implicitkwnames opened 10:55PM - 09 Jan 20 UTC (UTC) …

The reason I don’t do that is because different keywords go to different functions. I suppose I could make all my functions take an arbitrary amount of keywords and just ignore anything not specified, but that seems wrong. I see your point about macros, but I don’t really agree. All code depends on…

[image] dstarerstor: All code depends on variable symbols. when you type f(x=x ) which variable is named x definitely matters. The point is that only the value of x matters in this case. You could have called it absolutely anything and it would not matter. Take any piece of code without mac…

[image] ExpandingMan: The point is that only the value of x matters in this case. You could have called it absolutely anything and it would not matter. Take any piece of code without macros, and transform it by mapping all symbols to new symbols, and it still works. I guess it depends on how …

One thing why not to do so is potential WTFs with macros. Say: f(; kw) = kw kw = 2 f(; kw) # supposedly works @some_macro let kw = 42 f(; kw) # error due to name mangling by the macro end If you want that behavior in your code and can get it with a macro, that’s perfectly fine and is a julia…

I didn’t fully understand the conversation, but have you seen this https://github.com/mauro3/Parameters.jl/blob/master/README.md , it might be a relevant package.

I really like this idea, and I would probably use it a lot if it got implemented. I’ll even go as far as saying that with this feature I’d use keyword arguments a lot more than I do now.

Relevant issue: https://github.com/JuliaLang/julia/issues/29333 . The syntax would also naturally extend to named tuples so that (; a, b) would be syntax for (a = a, b = b).

This can be implemented in a package: using MacroTools: @capture, splitarg macro pun(ex) ret = if @capture ex (f_(args__; kw__)) kw = map(kw) do kwarg key, typ, splat, val = splitarg(kwarg) if splat kwarg elseif val == nothing …

This macro actually works great with no extra cost (which my previous did have). Thanks! I’ll be using this until the feature is added, or forever if its not

Keyword arguments without a keyword?

Internals & Design

StefanKarpinski December 5, 2019, 12:49pm 8

One could get around that by doing the expansion of f(; kw) to f(; kw=kw) before doing macro expansion. Then the macro would rewrite it to f(; kw=var”##3#kw”) or something.

Topic		Replies	Views
Weird macro behavior trying to simulate keyword arguments General Usage	8	1107	November 21, 2018
Metaprogramming function with keyword argument General Usage macros , metaprogramming	2	1249	July 21, 2018
Passing duplicate key in function through `kwargs` doesn't error Internals & Design question	1	281	December 20, 2023
Keyword name disambiguation General Usage	5	916	August 22, 2017
Argument confusion when calling macro with semicolon parameter syntax General Usage macros	7	553	September 13, 2023

Keyword arguments without a keyword?

Related topics