You can use the __init_subclass__ method which was introduced in Python 3.6 to make customizing class creation easier without resorting to metaclasses. When defining a new class, it is called as the last step before the class object is created. In my opinion, the most pythonic way to use this would be to make a … Read more
You can’t do that. Interfaces, abstract, etc. cannot apply to static members. If you want to accomplish this, you will have to manually remember to do it on all deriving classes. Also, static members are inherited by deriving classes. Child classes must hide the static parent member if they wish to specify alternate behavior.
I’d suggest adding a custom JsonDeserializer for Nodes: Gson gson = new GsonBuilder() .registerTypeAdapter(Node.class, new NodeDeserializer()) .create(); You will be able to access the JsonElement representing the node in the deserializer’s method, convert that to a JsonObject, and retrieve the field that specifies the type. You can then create an instance of the correct type … Read more
Was just struggling with a similar problem myself, and this seems to work for me: type Constructor<T> = Function & { prototype: T }
Since C++ has multiple inheritance unlike C# and Java, yes you can make a series of abstract classes. As for convention, it is up to you; however, I like to precede the class names with an I. class IStringNotifier { public: virtual void sendMessage(std::string &strMessage) = 0; virtual ~IStringNotifier() { } }; The performance is … Read more
The answer is the same for java: THere’s no reason for a public constructor for an abstract class. I’d assume that the reason that the compiler doesn’t complain is as simple that they just didn’t spend time covering that since it really doesn’t matter if it’s public or protected. (source) You can’t call a constructor … Read more
There’s a bit of a story behind interfaces in Python. The original attitude, which held sway for many years, is that you don’t need them: Python works on the EAFP (easier to ask forgiveness than permission) principle. That is, instead of specifying that you accept an, I don’t know, ICloseable object, you simply try to … Read more
Short Answer: No. Long Answer: It is not the base class or the number of ancestors a class has in its hierarchy that affects it speed. The only thing is the cost of a method call. A non virtual method call has a cost (but can be inlined) A virtual method call has a slightly … Read more
A Virtual/Abstract field? No. Fields are just there to hold data. There’s nothing to implement. You can define a Virtual/Abstract Property though.
What we are having here is two different methods with individual type parameters each. public abstract <T extends AnotherClass> void getAndParse(Args… args); This is a method with a type parameter named T, and bounded by AnotherClass, meaning each subtype of AnotherClass is allowed as a type parameter. public <SpecificClass> void getAndParse(Args… args) This is a … Read more