You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think one can easily come up with an implementation of the Optimizer interface but the methods seems hardcoded in the optimizer methods file as constants, so there's no way to extend that and make a new implmentation detectable by the library. Is that by design or maybe there is a workaround for that ? I want to implement some tweaked optimizers for my specific use case that have no business being part of the library, so i think a clear interface with some more docs and a register method would be great additions.
The text was updated successfully, but these errors were encountered:
I think one can easily come up with an implementation of the Optimizer interface but the methods seems hardcoded in the optimizer methods file as constants, so there's no way to extend that and make a new implmentation detectable by the library. Is that by design or maybe there is a workaround for that ? I want to implement some tweaked optimizers for my specific use case that have no business being part of the library, so i think a clear interface with some more docs and a
register
method would be great additions.The text was updated successfully, but these errors were encountered: