Ryan Nett
Ryan Nett
Also @JimClarke5 I don't think this is an error, it looks like it's just a check failure. What changes if you run `spotless:apply` (commit or save what you have, first)?
And the reason for that error is that when you change a file with the copyright, it extends the time to the current year, so it wants to change 2020...
Optimizers will probably want to (only?) support the new variables, so you may want to wait for that. It would be nice if there was an option to pass in...
I agree w/ `init`, I was doing something similar in Kotlin w/ delegates, so supporting that is nice. It might be nice to have a overloadable, class-scoped `init` but also...
This applies to `Layer`, as well.
It would be nice to not have to expose it to the user, i.e. something like: ```java abstract class Activation { private List initers = new ArrayList(); private boolean inited...
Right, duh, there should be a flag, edited it. The init logic should probably be moved to a synchronized method.
I don't see the issue with 1, it's still re-creating all the operations, just in the same scope or a new one. And since you're passing in operands you almost...
Hmm, yeah, it seems like there's a definite dichotomy between stateful/graph linked classes like `Optimizer` and `Metric` and stateless ones like `Activation`, `Loss`, `Regularizer`, etc. I would be fine with...
The other option would be to always use eager variables for the state, like is done in functions. But again, I don't think that's worth doing for the few stateful...