# Why are missing values not ignored by default?

**URL:** <https://discourse.julialang.org/t/why-are-missing-values-not-ignored-by-default/106756>\
**Category:** Internals & Design\
**Tags:** data, missing-values\
**Created:** [November 26, 2023, 1:45am UTC](https://discourse.julialang.org/t/why-are-missing-values-not-ignored-by-default/106756 "2023-11-26T01:45:36Z")\
**Posts on this page:** 1\
**Showing post:** 48

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [November 27, 2023, 3:58pm UTC](https://discourse.julialang.org/t/why-are-missing-values-not-ignored-by-default/106756/48 "2023-11-27T15:58:54Z")

</div>

> [@lmiq](#):
>
> Seems to me from the discussion that the best would be to have a package that deals with another type, such as `unsafe_missing`, that implemented all the functions desired, so that someone can just replace all the `missing`s in their data with that one and move forward with their preferred choice.

It would make it easier to do something like that if we added a new supertype `AbstractMissing >: Missing` to the `Base` package. (This can be done in 1.x — adding a new supertype is not considered a breaking change IIRC.)

That way, a lot of packages like DataFrames.jl could more easily support alternative `missing` types, e.g. an `ImputedMissing` type with some kind of semantics of automatic imputation, without having to specifically depend on new packages.

---

_[View the full topic](https://discourse.julialang.org/t/why-are-missing-values-not-ignored-by-default/106756)._
