# Base.@kwdef for v1.0?

**URL:** https://discourse.julialang.org/t/base-kwdef-for-v1-0/21954
**Category:** Internals & Design
**Created:** [March 17, 2019, 5:08am UTC](https://discourse.julialang.org/t/base-kwdef-for-v1-0/21954 "2019-03-17T05:08:53Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [March 17, 2019, 5:56am UTC](https://discourse.julialang.org/t/base-kwdef-for-v1-0/21954/2 "2019-03-17T05:56:57Z")

</div>

FWIW, I think you should just depend on 1.1, eg specify something like

```nohighlight
[compat]
julia = "1.1"

```

in your `Project.toml`. This is what I am doing for almost all of my packages (yes, I love `Base.@kwdef` too, and I am removing a lot of workarounds as the 1.1 compiler is so much smarter than 1.0).

Generally, it is my impression that features will not be backported, just critical bug fixes. Which is as it should be: with a lot of backports, one could hardly commit to keep a branch “stable”.

See the [some discussion starting here](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623/35).

---

_[View the full topic](https://discourse.julialang.org/t/base-kwdef-for-v1-0/21954)._