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

ch4 composition: add not about composition being "associative" #182

Open
getify opened this issue May 2, 2019 · 1 comment
Open

ch4 composition: add not about composition being "associative" #182

getify opened this issue May 2, 2019 · 1 comment

Comments

@getify
Copy link
Owner

getify commented May 2, 2019

compose(compose(fn3,fn2),fn1) ~=~ compose(fn3,compose(fn2,fn1))
@godhand4826
Copy link

godhand4826 commented Jun 12, 2019

As I know...
Sets are types for programmer.
If I write a function that given the same type of input(e.g. 1, 2, 3) and returns different type of output(e.g. 'a', 5, True), that will not be a set function which makes composition failed. Since composition is failed, it's no need to check if the composition being associative.
If the function is just evaluate(mapping) from one type to another type(maybe the same). It will be a set function. Set functions's composition is always associative in category of set(Sets).
If I'm wrong just let me know. Have a good day.

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

No branches or pull requests

2 participants