The expected behaviour when adding option deprecated = true to a message is for the compiler to inject a Base.depwarn, currently this gets injected in the module scope and gets suppressed during precompilation. IMO it should be injected as part of the generated constructor so that the deprecation warning is emitted when the constructor is first called.
The expected behaviour when adding
option deprecated = trueto a message is for the compiler to inject aBase.depwarn, currently this gets injected in the module scope and gets suppressed during precompilation. IMO it should be injected as part of the generated constructor so that the deprecation warning is emitted when the constructor is first called.