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

Alias for input Signals #128

Open
JobJob opened this issue Mar 20, 2017 · 1 comment
Open

Alias for input Signals #128

JobJob opened this issue Mar 20, 2017 · 1 comment

Comments

@JobJob
Copy link
Member

JobJob commented Mar 20, 2017

Previously you could use e.g. Input(2) to create an "input" signal, now you use Signal(2). Should we add an alias to Signal, e.g. input? It would be more consistent with the other operators that create Signals that all have lower case names (map, filter, etc), and more intuitive, to me at least.

@shashi
Copy link
Member

shashi commented Apr 9, 2017

Sounds fine to me! I quite like how the capitalization in Signal denotes the fact that it's a constructor though.

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

2 participants