TaskEx index

Open

#139 opened on Jan 5, 2023 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Active
Tech stack: fsharp
Domain: backend-api-design

Research direction

Start by reading the replaced issues #128 and #129, the linked proposals #140–#143, and the naming discussion in fslang-suggestions issue #1042. The issue does not name files or tests; completion requires narrowing the helper scope and settling stable APIs that follow FSharp.Core conventions.

Written by the indexing model from the issue text.

Description

feature request topic: task-ex

Replaces https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/128 https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/129

Within the F# ecosystem, there are a number of commonly used augmentations that typically get maintained as internal helpers within libraries and applications, manually copied around in various ways. Examples of such helpers:

#140 Async.ignore / Task.ignore / ValueTask.ignore
#141
#142
#143

While it can be argued that many of these concerns should be addressed in FSharp.Core, these are being logged here first in an attempt to narrow down the number of suggestions, with a view to getting stable naming (and potentially a shims library of some kind as a stopgap). NOTE that building a one stop shop for lots of arbitrary helpers is a non-goal of this effort.

NOTES:

naming discussion regarding Immediate/Background/Synchronously. The proposed APIs should adhere strongly to the conventions of FSharp.Core

Dominant language: F#
Stars: 111
Forks: 13
Avg merge: 7h 59m
Merged PRs (30d): 3

Contributor guide

Open the contributing guide

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.