Create eager-mode evaluation of onnxscript functions about onnxscript HOT 3 CLOSED

Fixed by #15?
If not, what is left to do?

from onnxscript.

I think the following needs to be done (mostly to ensure consistency between eager-mode and onnx-conversion):

• Will need type-checking to ensure types of arguments passed in (for eager-mode) are of correct expected types
• This will be better off if we define our own types/classes (e.g. our own tensor-types, that may be a wrapper around numpy arrays) and if these are consistent with the type-annotations we use (such as FLOAT[100]). At any rate, we should have a clear definition of what representation-type we use for what onnx-types.

Further, we should be able to do the following (not sure it is there yet): simply import the function-definitions, and call them as normal python functions. Just like in the example shown above for gemmgelu, but I think some clean up may be required (such as special handling of the identifier oxs etc.)

from onnxscript.

Looks like this is done.

from onnxscript.