lisa VS blazon

You might be interested in that: https://github.com/ARM-software/lisa/blob/master/lisa/monad.py

This is to replace the current flow purely based on pandas dataframe and offline trace.dat parsing used in LISA: https://github.com/ARM-software/lisa (collecting a trace.dat is nice for debugging but limits to small durations, and pandas does not allow running computations in constant memory, which is an issue for very big traces)

The module added by this PR seems to be a pretty good fit: https://github.com/ARM-software/lisa/pull/1722

I made that thing taking some vague inspiration from SML module system: https://github.com/ARM-software/lisa/pull/1722/files

import builtins from operator import add import functools # These functions can be found at: # https://github.com/ARM-software/lisa/blob/master/lisa/utils.py#L147 # Note: my implementation of curry() seems to be broken wrt named parameters (or for parameters with defaults, haven't looked at the details) for some reason but for this example it does not matter from lisa.utils import compose, curry def even(x): return x % 2 == 0 # The builtin functions don't have a signature, which will upset curry() so we # redefine it here def map(f, iterable): return builtins.map(f, iterable) def filter(f, iterable): return builtins.filter(f, iterable) # Swapped init and iterable to be curry-friendly def reduce(f, init, iterable): return functools.reduce(f, iterable, init) def pipeline(*items): # Add a currying layer so that we spare the user the need to do it return compose(*(curry(f)(*args) for (f, *args) in items)) # x = filter(even, list) |> map(lambda x: x+1) |> reduce(+) f = pipeline( (filter, even), (map, lambda x: x+1), (reduce, add, 0), ) l = [1,2,3,4] x = f(l) print(x)

Making a general ORM is actually a pretty hard problem. You need to map schemas/constraints between systems. If anyone wants some inspiration, I started a library that does this, very alpha: https://github.com/DeadWisdom/blazon