These functional API advantages seem like they could also be implemented in a sub-classing style (though they haven’t been yet.) Classes are perfectly capable of holding/serializing/being reconstructed from data structures, including graphs and input shapes. What am I missing?https://twitter.com/fchollet/status/1414667159326715908 …
-
Personally, I like the sub-classing style, but the advantages you cited of the functional API are real and important, so I’m thinking about what it would look like if the sub-classing style had them too.
I see, I think you may be thinking of the following style -- basically a Functional model, but defined by subclassing the `Model` class (which is useful for packaging and for adding/overriding methods, like `train_step`/ etcpic.twitter.com/dG7XxxtCo8
-
-
But if you want to decouple these extra methods from the model-definition style, you can also just do this:pic.twitter.com/M9QerkFCJ0
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yeah, I suppose that covers a lot of what I was thinking. It seems like serializing/deserializing a model like that would avoid the bytecode issue, etc. The ergonomics do seem a bit clunky compared to the functional API though.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.