fsprojects / fsprojects/FSharpPlus
Revisit Computation Expressions design
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 941
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
I'm opening this issue as a centralized place to discuss and review the current design of the generic Computation Expressions.
The main issue of the current design was highlighted by @cmeeren recently and has to do with the "autosense" design decision, to allow to figure out automatically in many trivial cases the evaluation strategy of the Computation (lazy vs strict).
We can discuss to change it, make it more explicit, or add another set of builders that are more strict and keep backwards compatibility.
Please raise all your questions, opinions, proposals, here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reviewing the current generic Computation Expressions implementation and the autosense behavior described in the issue, then follow the discussion to determine whether there is an agreed design. Done requires a settled proposal for the evaluation strategy and its compatibility implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100