Renaming OperatorImpl

Hello,

After experimenting with exports I came to the conclusion that maybe OperatorImpl are not so well named. Indeed this name sugest that it hold the Implementation (a.k.a the computation kernel).

However it is not the case!

As illustrated here, an OperatorImpl is an object holding a registry for all the CPU implementation of the Operator it is associated with (foir example a Conv2D).

I propose to rename OperatorImpl -> Backend. Object like ConvImpl1D_cpu -> Conv1DBackend_cpu.

Note: Maybe this will also result in changing attribute mBackend of Opertor to mBackendKey which IMO will also add clarity.

Note: I propose to also change naming of impl to follow convention Op<NbDims>D that was set with #168 (closed) in !163 (merged))

In current export the equivalent to an OperatorImpl is the ExportLib. So following this change I propose to also rename it as ExportBackend. This will rename ExportLibAidgeARM -> ExportBackendAidgeARM.

added Discussion 💬 label

@pineapple @olivierbichler Do you have thoughts on this ?

I know it is annoying to change again all the names but I think this will add clarity that will allow future devs to better understand what is the intent of each objects!

Cheers,

Cyril

changed the description

closed