Revert the original Optimizer behaviour, just fix it
Revert the original Optimizer behaviour, just fix it

The old 'scan for setting' approach is better when handling of
user-defined settings is needed. I just got it adapted for mutiple COREs
and SETTINGs loaded.

rakudo/rakudo,rakudo/rakudo,rakudo/rakudo,tbrowder/rakudo,rakudo/rakudo,softmoth/rakudo,tbrowder/rakudo,tony-o/rakudo,labster/rakudo,MasterDuke17/rakudo,tbrowder/rakudo,tony-o/rakudo,nbrown/rakudo,nbrown/rakudo,nbrown/rakudo,softmoth/rakudo,softmoth/rakudo,tbrowder/rakudo,nbrown/rakudo,MasterDuke17/rakudo,tbrowder/rakudo,nbrown/rakudo,tony-o/rakudo,salortiz/rakudo,salortiz/rakudo,labster/rakudo,tony-o/rakudo,tony-o/rakudo,labster/rakudo,labster/rakudo,softmoth/rakudo,MasterDuke17/rakudo,tbrowder/rakudo,salortiz/rakudo,salortiz/rakudo,softmoth/rakudo,MasterDuke17/rakudo,MasterDuke17/rakudo,tony-o/rakudo,rakudo/rakudo,labster/rakudo,MasterDuke17/rakudo,salortiz/rakudo,labster/rakudo,rakudo/rakudo,salortiz/rakudo,nbrown/rakudo