Generics don't make much sense in dynamic languages.
You don't need to cast to the correct class to call a method.
If the only selector you use is length then any object that responds to length will work.
You don't need to cast to the correct class to call a method.
If the only selector you use is length then any object that responds to length will work.
For example, if I have a news aggregator that keeps an array of 4-5 types of article objects, I may want to process them differently in a UITableView. I could store them all in the array and then do type checking at the time they should be rendered to determine how each are displayed. Of course, this can be achieved in statically typed languages as well if, say, each article class inherited from a common class, but what if they don't? On that note, does anyone know how this library handles inheritance?
This library would definitely help if you prefer the statically typed languages, but I would be wary of losing the freedom of Objective-C. Instead of binding data containers to types, perhaps good documentation and clearly written code is more the answer.