practicalli / practicalli/clojure

Side effects and side causes

Open
#277 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

design
Dominant language
Makefile
Stars
117
Forks
36
PR merge metrics
No merged PRs in 30d

Description

http://blog.jenkster.com/2015/12/what-is-functional-programming.html

Relates to designing Clojure with pure functions

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the linked article about functional programming and inspect the repository to determine where a discussion of side effects, side causes, and pure functions belongs. The issue does not name a file, entry point, or concrete documentation change, so the intended scope and definition of done need to be clarified before work begins.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.