I have a config object like this: using Parameters @with_kw mutable struct Config "Param 1" param1::Float64 # ... several other items ... "Whether to iterate randomly." use_random::Bool = false end And now I need to modify it like so, to enable more than 2 strategies: @with…

Not sure if that works for your non-MWE, but this is what I (got the ping from the linked post) ended up using: @kwdef mutable struct Config """Param 1""" param1::Float64 """Deprecated, please use `iter_strategy = "random"` instead.""" use_random::Union{Bool, Nothing} = nothing…

Yeah, I don’t love having the union of the fields in there, it creates some confusion in users of the Config object since both fields are still there. I’d prefer to take care of everything before/while creating the object and have no use_random field left.

FWIW I didn’t find a great solution to this at the constructor point, I ended up finding all the places in my code where a constructor is called and adjusting the calls there. If there were a way to call the @with_kw-generated constructor from a new constructor, that would be a great way to fix thi…

Wrapping kw-based Parameters.jl constructor, for deprecation

General Usage

Ken_Williams November 21, 2024, 7:27pm 2

FYI this is very similar to Catching deprecated keyword arguments (with Parameters.jl), which doesn’t currently have an answer.

Topic		Replies	Views
Catching deprecated keyword arguments (with Parameters.jl) General Usage	0	248	May 18, 2022
Deprecate keyword argument New to Julia question	2	976	June 22, 2023
Deprecating usage of keywords General Usage	2	753	December 16, 2016
Standard way to deprecate a keyword argument General Usage question	3	714	June 22, 2023
[ANN] DeprecateKeywords.jl – a macro for keyword deprecation Package Announcements	4	362	June 28, 2023

Wrapping kw-based Parameters.jl constructor, for deprecation

Related topics