希望为那些想要类似保护方法的人节省一些时间:

与其他答案一样，swift现在提供了“private”修饰符——它是按文件定义的，而不是像Java或c#那样按类定义的。这意味着如果你想要受保护的方法，如果它们在同一个文件中，你可以使用swift私有方法

创建一个基类来保存“受保护的”方法(实际上是私有的) 子类化这个类以使用相同的方法 在其他文件中，您不能访问基类方法，即使您创建了子类

文件1:

class BaseClass {
    private func protectedMethod() {
        
    }
}

class SubClass : BaseClass {
    func publicMethod() {
        self.protectedMethod()  //this is ok as they are in same file
    }
}

文件2:

func test() {
    var a = BaseClass()
    a.protectedMethod() //ERROR


    var b = SubClass()
    b.protectedMethod() //ERROR
}

class SubClass2 : BaseClass {
    func publicMethod() {
        self.protectedMethod() //ERROR
    }
}

现在在测试版4中，他们为Swift添加了访问修饰符。

from Xcode 6 beta 4 realese notes:

Swift access control has three access levels: private entities can only be accessed from within the source file where they are defined. internal entities can be accessed anywhere within the target where they are defined. public entities can be accessed from anywhere within the target and from any other context that imports the current target’s module. By default, most entities in a source file have internal access. This allows application developers to largely ignore access control while allowing framework developers full control over a framework's API.

till swift 2.0 there were only three access level [Public, internal, private] but in swift 3.0 apple added two new access level which are [ Open, fileType ] so now in swift 3.0 there are 5 access level Here I want to clear the role of these two access level 1. Open: this is much similar to Public but the only difference is that the Public can access the subclass and override, and Open access level can not access that this image is taken from Medium website and this describe the difference between open and public access

现在是第二个新的访问级别 2. 文件类型是更大版本的私有或更低的访问级别比内部 fileType可以访问[class, struct, enum]的扩展部分 而且private不能访问扩展部分的代码，它只能访问 词法作用域 这张照片取自Medium网站，描述了fileType和Private访问级别之间的区别

Swift 3.0提供了5种不同的访问控制:

开放 公共 内部 fileprivate 私人

Open access and public access enable entities to be used within any source file from their defining module, and also in a source file from another module that imports the defining module. You typically use open or public access when specifying the public interface to a framework. Internal access enables entities to be used within any source file from their defining module, but not in any source file outside of that module. You typically use internal access when defining an app’s or a framework’s internal structure. File-private access restricts the use of an entity to its own defining source file. Use file-private access to hide the implementation details of a specific piece of functionality when those details are used within an entire file. Private access restricts the use of an entity to the enclosing declaration. Use private access to hide the implementation details of a specific piece of functionality when those details are used only within a single declaration. Open access is the highest (least restrictive) access level and private access is the lowest (most restrictive) access level.

默认访问级别

如果您自己没有明确指定访问级别，那么代码中的所有实体(除了少数特定的例外)都有一个默认的内部访问级别。因此，在许多情况下，您不需要在代码中指定显式的访问级别。

关于该主题的发布说明:

Classes declared as public can no longer be subclassed outside of their defining module, and methods declared as public can no longer be overridden outside of their defining module. To allow a class to be externally subclassed or a method to be externally overridden, declare them as open, which is a new access level beyond public. Imported Objective-C classes and methods are now all imported as open rather than public. Unit tests that import a module using an @testable import will still be allowed to subclass public or internal classes as well as override public or internal methods. (SE-0117)

更多信息和细节: Swift编程语言(访问控制)

据我所知，没有关键词“公共”，“私人”或“受保护”。这意味着一切都是公开的。

然而，苹果可能希望人们使用“协议”(世界上其他地方称为接口)和工厂设计模式来隐藏实现类型的细节。

无论如何，这通常是一个很好的设计模式;因为它允许您更改实现类层次结构，同时保持逻辑类型系统不变。

Xcode 6中引入的访问控制机制:

Swift provides three different access levels for entities within your code. These access levels are relative to the source file in which an entity is defined, and also relative to the module that source file belongs to. Public access enables entities to be used within any source file from their defining module, and also in a source file from another module that imports the defining module. You typically use public access when specifying the public interface to a framework. Internal access enables entities to be used within any source file from their defining module, but not in any source file outside of that module. You typically use internal access when defining an app’s or a framework’s internal structure. Private access restricts the use of an entity to its own defining source file. Use private access to hide the implementation details of a specific piece of functionality. Public access is the highest (least restrictive) access level and private access is the lowest (or most restrictive) access level.

默认在内部访问，因此不需要指定。还要注意，私有说明符不是在类级别上工作，而是在源文件级别上工作。这意味着要使类的某些部分真正私有，您需要将其分离到自己的文件中。这也介绍了一些关于单元测试的有趣案例……

我提出的另一个观点(在上面的链接中有评论)是，你不能“升级”访问级别。如果你子类化了某个东西，你可以对它进行更多的限制，但反过来就不行。

最后一点也会影响函数、元组和其他东西，例如，如果一个函数使用了私有类，那么将函数设置为内部或公共是无效的，因为它们可能无法访问私有类。这将导致编译器警告，并且您需要将该函数重新声明为私有函数。