Francesco Cameli

This perhaps requires removing the objects as `ptr` to something, and instead letting them be just normal nim's `object` types. They could be inheriting from a common `OmniStruct` object that...

What about `Data` though?

Should `Data` look at all the entries of each struct recursively and call the standard constructor, initializing all `Datas` along the way? What size should those `Datas` have though? Perhaps...

Perhaps this can confuse things a bit, not so sure.

But it's gonna be useful for `processes`, so that their output can be accessed by name and not by index

Hello! Thanks for the kind words and sorry for the late reply, the Github notifications don't really work that well with my computer, apparently :) WASM compilation is definitely one...

Also, this would require a new const mechanism for `def` arguments: ```nim def something_unroll(AMT): loop AMT i: #

Internally, `const` + `block` is the way to go: ```nim const mytable : array[100, float] = block: var t : array[100, float] for i in 0..

One more thing to think about is IFFT: do we want the whole FFT -> processing -> IFFT chain in one object?

> > One more thing to think about is IFFT: do we want the whole FFT -> processing -> IFFT chain in one object? > > Not sure what you...