# Expose \`Base.depwarn(...; force=false)\` in \`@deprecate\`

**URL:** https://discourse.julialang.org/t/expose-base-depwarn-force-false-in-deprecate/129383
**Category:** General Usage
**Tags:** deprecation
**Created:** [May 27, 2025, 2:31pm UTC](https://discourse.julialang.org/t/expose-base-depwarn-force-false-in-deprecate/129383 "2025-05-27T14:31:41Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![drbergman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/drbergman/32/202226_2.png) [@drbergman](https://discourse.julialang.org/u/drbergman)
#### Post date: [May 27, 2025, 2:31pm UTC](https://discourse.julialang.org/t/expose-base-depwarn-force-false-in-deprecate/129383/1 "2025-05-27T14:31:41Z")

</div>

Following up on the conversation in [Why is `depwarn=no` by default?](https://discourse.julialang.org/t/why-is-depwarn-no-by-default/51094) Would it be possible to expose the `force` kwarg of `Base.depwarn` in the `@deprecate` call? I just opened a PR in DeprecateKeywords.jl that uses the following syntax to do something similar there:

```julia
@depkws force=true function f(; a=2, @deprecate(b, a))
    a
end

```

The first argument here is optional (defaulting to `false`) and can be any expression that evaluates to a `Boolean`, including an assignment expression.

Could something similar be done with `@deprecate`? I expect my package to mostly be used by end users rather than incorporated into the dependencies of another package, and so I want to be able to communicate directly to endusers about the expected future state of the API.