Sorry to wake up the thread 3 years later, but it is the only Google-result that shows up :D
So, the deprecated message still shows up, but it seems to be working well. I am writing a small scene-graph for my render engine and wonder whether I should transition away from generic methods or not. Some details about my use case: Generic methods are usefull for me because of the following: The scene's tree nodes (entities in the scene) need to use runtime polymorphism, to allow different types of entities to be handled during runtime (and allow users of the library to add their own entity-types). So methods are unavoidable (I guess?). Now, e.g. my mesh-entity I implemented with generics, in order to allow the user of the API to just specify vertex type and index type (uint16/uint32) for the mesh. As far as I can see, the only other option to avoid generic methods here would be to have a macro that the API user can call to generate the non-generic method. So the question is, in case I need to worry about the future of generic methods: What would be a good alternative here? On the other hand nim 2.0 seems to not yet have abandoned generic methods?
