Results 342 comments of François Chollet

Yes, we could definitely add this op. Do you think it can be supported in all backends? Are you able to start a PR?

This has been added -- thanks for the contribution!

> I would be very interested to have this feature, just to feed the Tensors of shape (batch, None, C, F, ...) to a keras model We *might* support `RaggedTensor`...

@kernel-loophole please open an issue on the KerasNLP repo if you'd like to contribute this feature!

I don't think we should make changes to the base `Loss` API (i.e. let's restricts changes to the `CompileLoss` class). I also don't think we should make `loss.set_specs()` a public-facing...

> As far as I know, CompileLoss is the very first point where loss and the inputs (y_true, y_pred) meet, not to mention that the structures might already be nested....

Report from the other thread: We *might* support `RaggedTensor` in the future with the TF backend specifically (such a feature does not exist with other frameworks). However if you're just...

It looks like a config deserialization issue. If you have the model's code, you can: 1. Load the old model with the old Keras version 2. Save its weights via...

Looking at the config in the error message, I have a vague idea what might be going on. This is *not* the config of a Keras `BatchNormalization` layer. For instance,...

Thanks for the PR! We'd need to add some test with a custom layer with complex inputs to verify that it works (and make sure we won't break it in...