REBL is currently implemented by re-instanciating the Bud instance whenever there is a REBL operation, and manually copying over the state from the old instance. Needless to say, this is not ideal: instead, we should provide Bud APIs to implement the operations required by the REBL (e.g., add a new rule, add a new collection, etc. to a running Bud instance).
REBL is currently implemented by re-instanciating the Bud instance whenever there is a REBL operation, and manually copying over the state from the old instance. Needless to say, this is not ideal: instead, we should provide Bud APIs to implement the operations required by the REBL (e.g., add a new rule, add a new collection, etc. to a running Bud instance).