A
Andez
Guest
I had a chat with a colleague many moons ago about this subject, which kick started me to think more about encapsulation. And given what I have seen a lot over the last 8 years, I thought I would ask this question.
As default, in a lot of cases, developers always seem to use public everywhere. But with careful consideration, things could be easily be made internal or private. Additionally, classes can be sealed when there is intent not to allow inheritence.
So given this, is there any performance gains from this when using Visual Studio 2017/2019 IDEs, running builds, Roslyn code analysis?
Andez (Please mark as answer if it helps)
Continue reading...
As default, in a lot of cases, developers always seem to use public everywhere. But with careful consideration, things could be easily be made internal or private. Additionally, classes can be sealed when there is intent not to allow inheritence.
So given this, is there any performance gains from this when using Visual Studio 2017/2019 IDEs, running builds, Roslyn code analysis?
Andez (Please mark as answer if it helps)
Continue reading...
