C#属性的get、set为何均被称为Accessor而非分别称为Accessor与Mutator？

Great question—this is exactly the kind of terminology nuance that comes down to how C# formalizes properties versus the older Java-style getter/setter method pattern. Let’s break it down clearly:

1. The Traditional OOP Terminology (Pre-C# Properties) #

In classic OOP design (think Java, C++ before properties), we talk about:

• Accessor methods: Methods like get_Name() that retrieve a value (they "access" the data).
• Mutator methods: Methods like set_Name(string value) that modify a value (they "mutate" the data).

These are two distinct, independent methods—each with its own purpose and signature. This terminology makes sense here because you’re explicitly calling two separate functions.

2. C# Properties Are a Unified Language Construct #

C# properties are not just syntactic sugar for two methods (even though they compile to get_XXX and set_XXX under the hood). The language specification defines a property as a single member that encapsulates a value, with optional "access points" to read or write that value.

The C# specification intentionally refers to both the get and set components as accessors (specifically, a get accessor and set accessor) for two key reasons:

• Emphasizes the property as a single entity: When you use myObject.Name (to read) or myObject.Name = "Alice" (to write), you’re interacting with one property member—not calling two separate methods. The get and set are just ways to access that single member, either to retrieve its value or update it.
• Clarifies language-level abstraction: C# hides the method-level implementation details from developers. The goal is to let you think of Name as a value you can get or set, not as two functions you call. Calling both parts "accessors" reinforces that abstraction.

Example Comparison #

Let’s contrast the two models to make this concrete:

Traditional Method Pattern (Accessor/Mutator) #

private string _name;

// Accessor method
public string get_Name()
{
    return _name;
}

// Mutator method
public void set_Name(string value)
{
    _name = value;
}

C# Property Pattern (Two Accessors) #

public string Name { get; set; }

In the property version, Name is one member with two accessors—you don’t think of them as separate methods, so the traditional accessor/mutator labels don’t fit the language’s abstraction.

Bottom Line #

The terminology difference exists because C# treats properties as unified value containers, not pairs of independent methods. Calling both get and set "accessors" aligns with how the language wants developers to think about properties: as a single, abstracted value that you can interact with via read/write access points.

内容的提问来源于stack exchange，提问作者Nika