Christof
Christof
One pitfall that came to mind is if there should be some kind of "superset" logic in such a case. For example if someone declares `addresource(CUDADev)`, does (s)he still have...
In my understanding this was more about declaring capabilities. I didn't really consider shared dispatch. For that purpose `::Union{CUDADev,CUDALib}` seems easy enough (?) I am lacking data on this. I'll...
not so far, no
Sure. I'd say the whole RL side of things is pretty much up for grabs.
Since we are having this conversation, I experimented a little with trying to build on POMDPs in my attempt to design an RL package. i have a writeup of my...
do you have a minimal working example that shows what you'd like to be able to do?
Mhm, I have been away too long to be confident enough that I remember things correctly, but I think this should work: In essence most operations of this package don't...
I considered this I am pretty sure. The issue is that the augment function is free to choose if an operation is applied eagerly or lazily. So the indices in...
> So the indices in eager should match the indices in lazy That said. That statement is currently not true (if i remember correctly). So technically your first label was...
Actually, I really want to add these kinds of augmentation strategies. I just didn't get around to doing them yet. If that is something you'd be interested in contributing I'd...