Skip to content

Data structure is always the last argument #263

@pravdomil

Description

@pravdomil

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions