Currently watching the IQueryable of Bart De Smet and he has mentioned the current type (which I was eager for some time).
public abstract class, someexensational type {Private SomeExistentialType ()}} is a way to create it in public Abstract Intu Fu (); Create Public Entity Type () (Return new ConcreteType 1 (); } Private class concrete type 1: some extensible type {public override int () {// some implementation ...}} Private class concrete type 1: some extensile type {public override int () {// some implementation ...} } Private class concrete type 1: Some extensible type {public override intu fu () {// some implementation ...}}}
The idea is that if all solid squares are in a private nested class ( Or maybe just internal classes S) then you are only forced to use the interface.
Very much like.
I am not a big fan of challenging the developer or forcing them to do something specific in these ways. In C / C ++, I could understand the justification of PIMPL IDIOM, because in C ++ you have a lot of security in C # and .NET, but oh well.
Comments
Post a Comment