# Namespaces × submodules **URL:** \ **Category:** Pitches\ **Created:** [April 4, 2018, 11:28pm UTC](https://forums.swift.org/t/namespaces-x-submodules/11673 "2018-04-04T23:28:32Z")\ **Posts on this page:** 1\ **Showing post:** 48
**Author:** ![tim1724](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/tim1724/32/450_2.png) [@tim1724](https://forums.swift.org/u/tim1724)\ **Post date:** [May 17, 2018, 6:41pm UTC](https://forums.swift.org/t/namespaces-x-submodules/11673/48 "2018-05-17T18:41:17Z")
> [@masters3d](#): > > The whole premise of submodules is access control. I just can not think of another reason for submodules but access control. > > I must be missing something. Honestly, what am I missing? See this thread: > [@"Submodule" is an ambiguous term](https://forums.swift.org/t/submodule-is-an-ambiguous-term/12484): > > A request from me: if you use the word "submodule" to refer to any particular feature or design, please explain what you're using it for. People have a lot of different features they want in Swift that could be called "submodules", and there's not one agreed-upon design that people will understand when you say the word. I'll try to list the most common requests / proposals below. (Note that many proposed designs have combined more than one of these features. I've tried to decompose them for the … --- _[View the full topic](https://forums.swift.org/t/namespaces-x-submodules/11673)._