Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

encoder usage requires split #1

Open
olilarkin opened this issue Feb 11, 2017 · 1 comment
Open

encoder usage requires split #1

olilarkin opened this issue Feb 11, 2017 · 1 comment

Comments

@olilarkin
Copy link

it seems counterintuitive to me that if I create a N order encoder there will be many inputs and I need an extra split operator e.g. :

declare name "Faust Effect";
import("stdfaust.lib");
process = _ <: ho.encoder(5, _, 0.5);

is there any case when an encoder would have more than 1 input? in which case wouldn't it be better if this split was unnecessary? is this an unavoidable artefact of the pattern matching technique used?

@olilarkin
Copy link
Author

of course I can write process(x)... , but would rather not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant