As noted by @Khoroshevskyi we'll still for the moment have indirect/transitive dependency on attmap through some other projects which continue to use it, but this removes looper's direct dependency on attmap.
Close #345
This does a handful of other things like tweaking function names and local variable names for readability, moving a variable declaration closer to where the value (a collection) is then built up, and minimizing number of pipeline interface instances which are built by moving an iteration-independent construction of one out of a for loop, such that it's just done once at the beginning of the loop. But the majority of the changes are directly related to the removal of attmap dependency (in favor of YAMLConfigManager over AttMap or its subtypes).
As noted by @Khoroshevskyi we'll still for the moment have indirect/transitive dependency on attmap through some other projects which continue to use it, but this removes looper's direct dependency on
attmap.Close #345
This does a handful of other things like tweaking function names and local variable names for readability, moving a variable declaration closer to where the value (a collection) is then built up, and minimizing number of pipeline interface instances which are built by moving an iteration-independent construction of one out of a for loop, such that it's just done once at the beginning of the loop. But the majority of the changes are directly related to the removal of
attmapdependency (in favor ofYAMLConfigManageroverAttMapor its subtypes).