[API] [Layers] introduce separate Layer's subclasses to represent number of layer's inputs

[knok16]

public sealed class Layer

public abstract class NoInputsLayer : Layer() {
    public abstract fun build(tf: Ops)

    public abstract fun computeOutputShape(): Shape

    public abstract fun forward(
        tf: Ops,
        isTraining: Operand<Boolean>,
        numberOfLosses: Operand<Float>?
    ): Operand<Float>
}

public abstract class SingleInputLayer : Layer() {
    public abstract fun build(tf: Ops, inputShape: Shape)

    public abstract fun computeOutputShape(inputShape: Shape): Shape

    public abstract fun forward(
        tf: Ops,
        input: Operand<Float>,
        isTraining: Operand<Boolean>,
        numberOfLosses: Operand<Float>?
    ): Operand<Float>

    public operator fun invoke(layer: Layer): Layer
}

public abstract class MultipleInputsLayer : Layer() {
    public abstract fun build(tf: Ops, inputShapes: List<Shape>)

    public abstract fun computeOutputShape(inputShapes: List<Shape>): Shape

    public abstract fun forward(
        tf: Ops,
        input: List<Operand<Float>>,
        isTraining: Operand<Boolean>,
        numberOfLosses: Operand<Float>?
    ): Operand<Float>

    public operator fun invoke(layer1: Layer, layer2: Layer, vararg otherLayers: Layer): Layer
}

Benefits:

• Main benefit is that the arity of a layer will be checked by compiler
• Using Functional builder it will not be possible to write the next code:
  • Add()(x) - there is no a point in adding single input
  • Softmax()(x, y, z) - Softmax layer accept a single input layer and in current implementation will just ignore y and z layers - which can create confusion
• Layers will not have methods that doesn't make sense for them (for example computeInputShapeFromIncomingLayers for Input layer)
• Sequential builder can be restricted to accept only SingleInputLayer layers since it doesn't make to pass multiple input layers there

Reference knok16@8643a87

[zaleslaw]

It's a great proposal, please prepare a PR for that.

I have one minor note for that: I suppose the basic class Layer should not be sealed at all, because we need to give the ability to write a custom Layer class in user code.