query: What's the best way to handle type indicators in object-oriented design?
positive_passages.docid: 145184
positive_passages.text: Object-oriented design: Saving complex objects
negative_passages.docid: 131176
negative_passages.text: Collection versus List what should you use on your interfaces?
negative_passages.docid: 64107
negative_passages.text: Finding the type of an object in C++
negative_passages.docid: 46812
negative_passages.text: Object Oriented pattern in C?
negative_passages.docid: 76045
negative_passages.text: How to determine if a type implements a specific generic interface type
negative_passages.docid: 71499
negative_passages.text: Casting of objects to dynamic types at runtime
negative_passages.docid: 77898
negative_passages.text: How to annotate deprecation of a class in Java?
negative_passages.docid: 83007
negative_passages.text: Developing C wrapper API for Object-Oriented C++ code
negative_passages.docid: 98143
negative_passages.text: How To Detect If Type is Another Generic Type
negative_passages.docid: 102268
negative_passages.text: Rule of thumb for choosing an implementation of a Java Collection?
negative_passages.docid: 114264
negative_passages.text: How to test enum types?
negative_passages.docid: 98374
negative_passages.text: Can I have polymorphic containers with value semantics in C++?
negative_passages.docid: 105387
negative_passages.text: How do I type hint a method with the type of the enclosing class?
negative_passages.docid: 148248
negative_passages.text: Check if object is Class type
negative_passages.docid: 42061
negative_passages.text: Identifying primitive types in templates
negative_passages.docid: 32337
negative_passages.text: Dynamically find the class that represents a primitive Java type
negative_passages.docid: 57077
negative_passages.text: Run-time Polymorphism in Java without "abstract"?