Kyle Daruwalla

Cool, glad to see someone trying this code out in a different use case than mine. The branch that I'm currently using for my research is `kd/refactor`. Unfortunately, it isn't...

Yes this project has seen no updates while Flux and CUDA have had many. The existing Project.toml probably needs up to date compatibility bounds. Or ideally, the package should be...

> Also, I have fortunately had some extra time lately to help get this package started, but unfortunately that will usually not be the case. I'm hoping that we can...

I haven't worked on that package for some time, but when I was working on it, the point was - be pure Julia (I don't think JuliaReinforcementLearning supported anything other...

Maybe it's just me, but I am getting confused here. > Given the importance that provided will have, I think we should include checks for it, e.g. in requirements_met. I...

Okay that clears a lot up. Based on that description, I think we need args + types as part of requirements for the `requirements_met` check to be reliable. If these...

Yes, I would avoid introducing a type hierarchy unless it provides something via dispatch (usually performance). I think a good alternative to ensure consistency across implemented environments is to write...

Yeah that's true. Maybe making a PR to add Cartesian products + rand would be either than writing the whole thing from scratch. Either way out of the scope of...

The previous "interface" was to import the corresponding AD package and just call e.g. `Tracker.withgradient`. The most recent attempt was supposed to be DI.jl, but the choice to focus on...

Going along Brian's point, even if we were to include this, I think it ought to be a function not a struct. Though I tend to lean towards not including...