4 Replies
easiest way is to have some base class for ReportSetup, that doesn't have the generic
@vec![atreit; 1024] That's what I figured. For what I'm trying to do, is this the right approach, or is there another way that would be better suited for the task?
No, it should be the approach to do what you said - a base class/interface that would be used to represent said classes in a collection. The question is whether you want the right thing? Is there a real need to have a collection of these different generic class instances?
Was this issue resolved? If so, run
/close
- otherwise I will mark this as stale and this post will be archived until there is new activity.