This is a rather old topic: Are setters and getters good or evil?
My question here is: do compilers in C++ / D / Java inline the getters and setter?
To which
Depending on the expected evolution of your class, get/setters may clutter your code vs. give you the flexibility to extend your implementation without affecting the client code.
Often I encounter classes that are used as 'data containers', which have both getter and setter for each member. That's nonsense. If you don't expect to need some 'special' functionality to be triggered when getting or setting a member, don't write it.
Given the speed of the machine, the effort of writing the extra abstraction will cost your clients more money.
Most compilers can optimize trivial getters/setters, but as soon as you declare them virtual (in C++), you pay an extra lookup - often worth the effort.