Remove Config() constructor in favor of explicit API for creating devices

Open stellaraccident opened this issue 5 years ago • 6 comments

It is currently very easy when doing non default construction of a SystemContext to create multiple Config instances for the same device. The API needs to provide a mechanism to create one and only one Config per driver/device. Since this will need to be substantially upgraded for eventual multi-device config at some point, it would be good as a short term measure to have an explicit API like get_default_config_for_driver() that can enforce the proper lifetimes until we build the general solution (this will keep things from spidering).

Reported from a customer.