shared resources across SearchConfigs (global builders) #390
Description
currently, any traversal/access/frontier models are siloed to exactly one edge list. however, when working with multiple edge lists, it can be helpful if resources can be built and shared across multiple edge lists. this can address:
- situations where the exact same model is set on multiple edge lists and therefore is duplicated in memory
- where a configuration does not guarantee it will produce idempotent models, and we want to guarantee it can