# Kotlin to support package protected visibility

**URL:** <https://discuss.kotlinlang.org/t/kotlin-to-support-package-protected-visibility/1544>\
**Category:** Language Design\
**Created:** [March 18, 2016, 11:05am UTC](https://discuss.kotlinlang.org/t/kotlin-to-support-package-protected-visibility/1544 "2016-03-18T11:05:14Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![eygraber](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/eygraber/32/2215_2.png) [@eygraber](https://discuss.kotlinlang.org/u/eygraber)\
**Post date:** [December 1, 2016, 11:31pm UTC](https://discuss.kotlinlang.org/t/kotlin-to-support-package-protected-visibility/1544/11 "2016-12-01T23:31:30Z")

</div>

Couldn’t agree more.

I think `internal` has its best use cases for libraries, or large projects that are modularized. Package should cover projects that aren’t modularized. Would make life much easier.

While we’re at it, is there any way to implement file level visibility?

```auto
// file.kt

class Foo private constructor(i: Int) {}

class Bar {
  fun baz() = Foo(0)
}

```

---

_[View the full topic](https://discuss.kotlinlang.org/t/kotlin-to-support-package-protected-visibility/1544)._