Francesco Cameli

That's alright, thanks for the swift response! I'll check again in the future

Thanks for this snippet, @madskjeldgaard ! It's super useful, similar to ScIDE's Ctrl + I. One quick thing,given the `scnvim_fuzzy.lua` file name, the two lines: ```lua vim.cmd("command! SCNvimFuzzyHelp lua require('scnvim_extra').scnvim_fuzzy_help()")...

`struct` will then become just a way to declare custom data types (like a `Vector[T]`). `process` will become the standard way of defining re-usable DSP code.

`Sine.omni` ```nim process Phasor: ins 1: freq outs 1 init: phase = 0 #internal def (can access ins) def updatePhase(): freq_incr = freq / samplerate phase = (phase + freq_incr)...

`chain` could also be used inside `process` in place of `sample`. `chain` and `perform` / `sample` are mutually exclusive.

What about writing a `def` with a `process` as argument? 1) They must always be type declared (probably) 2) Can only be called in `sample` (as they in turn call...

You could also compile `process` directly: 1) If file contains multiple processes, they all will get compiled (if no `perform` / `sample` OR `chain` are provided): `omni Sine.omni` 2) To...

What about `Buffer` as one of the `ins`? That will require to be passed in on creation? ```nim process Something: ins 1: buf {Buffer} ... ins 1: buf {Buffer} init:...

Related to #1

This can easily be solved by taking the same approach that has been taken for Datas in #67