It’s because it’s impossible to conform to a protocol at any access level other than the access level of the protocol itself. In other words, if you have a public protocol, you cannot have private conformance to it. This is partially because protocol conformance is something that can be queried for at runtime (and therefore … Read more
Are protected members/fields really that bad? No. They are way, way worse. As soon as a member is more accessible than private, you are making guarantees to other classes about how that member will behave. Since a field is totally uncontrolled, putting it “out in the wild” opens your class and classes that inherit from … Read more
Actually there is a complete and simple solution to this problem that doesn’t involve modifying the client code or creating an interface. This solution is actually faster than the interface-based solution for most cases, and easier to code. public class Journal { private static Func<object, JournalEntry> _newJournalEntry; public class JournalEntry { static JournalEntry() { _newJournalEntry … Read more