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.

Sign up for GitHub

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

Jump to bottom

Data structure is always the last argument #263

Open

pravdomil opened this issue May 31, 2021 · 0 comments

pravdomil commented May 31, 2021 •

edited

Loading

Hello,

I would rephrase following:

Elm also uses the convention that the data structure is always the last argument across the ecosystem.

Because in following case it is not clear:

insertDocument : a -> Database a -> Task x ()
readDocument : Id a -> Database a -> Task x a

-- or

insertDocument : Database a -> a -> Task x ()
readDocument : Database a -> Id a -> Task x a

I think that:
It is not matter of: subject/data structure/module structure.
It is matter of: how function get used (partial application/pipes)

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