# Proposal: Private modules (implementation specific) (closed)

**URL:** <https://forum.elixirforum.com/t/proposal-private-modules-implementation-specific-closed/19361>\
**Category:** Elixir News\
**Tags:** official-proposal\
**Created:** [January 14, 2019, 10:44pm UTC](https://forum.elixirforum.com/t/proposal-private-modules-implementation-specific-closed/19361 "2019-01-14T22:44:38Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![JEG2](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/jeg2/32/936_2.png) [@JEG2](https://forum.elixirforum.com/u/JEG2)\
**Post date:** [January 15, 2019, 2:38am UTC](https://forum.elixirforum.com/t/proposal-private-modules-implementation-specific-closed/19361/7 "2019-01-15T02:38:53Z")

</div>

I find myself not wanting this change. It feels like a lot of special cases, for mild protection. I feel like people who use code with something like `@moduledoc false` on it today know what they are doing and will not be deterred by this feature. The protection is easily defeated as shown in this thread.

Maybe I just haven’t felt the pain this feature is targeted at though. Perhaps a good example use case would help me see the value.

---

_[View the full topic](https://forum.elixirforum.com/t/proposal-private-modules-implementation-specific-closed/19361)._
