private:
 string m_name;
 std::string Name() const { return m_name; }
 void Name(std::string val) { m_name = val; }

• What if I want the names to be get/setName, which is more common?


• What if these should be public, as most encapsulated methods tend to be?

const $SymbolType$& Get$GeneratedPropertyName$() const { return $SymbolName$; }
$ClassName$& Set$GeneratedPropertyName$(const $SymbolType$& val)
{
    $SymbolName$ = val;
    return *this;
}

const $SymbolType$& Get$GeneratedPropertyName$() const { return $SymbolName$; }
// $ClassName$&
void Set$GeneratedPropertyName$(const $SymbolType$& val)
{
    $SymbolName$ = val;
    return *this;
}

const $SymbolType$& Get$SymbolName$() const { return $SymbolName$; }
$ClassName$& Set$SymbolName$(const $SymbolType$& new_value)
{
    $SymbolName$ = new_value;
    return *this;
}

class abc
{
   int Apple;
}

void func()
{
    abc obj;
    obj.Apple = 5;
}

quote:

---

We're planning to update references as well. Would you want to keep that one enabled?

---

template <typename T>
class AClass
{
// Public types
public:

    typedef T value_type;
    
    ... There could be protected or private types here but omitted if not used.
    
    ... This is where encapsulate field currently places the accessors (without comments)
    
// Public functions
public:

    /// Constructor
    AClass() {}
    
    ... This is where I want to put the accessor functions when I encapsulate field
    ... and I want to take the comment with them, so what I want is this:
    
    /// Comment for the variable
    const value_type& GetVar() const { return Var; }
    void SetVar(const value_type& var) { Var = var; }
    
// Protected functions (typically virtuals)
protected:

    ...
    
// Private functions
private:
    ...
    
    ... In very rare circumstances there could be public or protected member variables here
    
// Private data 
private:
    
    /// Comment for the variable
    value_type Var;
   
};

quote:

---

could I place a request for it.

---