fsharp / fsharp/fslang-suggestions
(List/Array/Seq).try(Average/AverageBy/Max/MaxBy/Min/MinBy/Reduce/ReduceBack/Skip/SplitAt/Tail/Take)
- Dominant language
- No language data
- Stars
- 373
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
# (List/Array/Seq).try(Average/AverageBy/Max/MaxBy/Min/MinBy/Reduce/ReduceBack/Skip/Tail/Take)
I propose we add try versions of all the remaining partial functions that do not have a try version already.
The existing way of approaching this problem in F# is either exception as control flow or duplicated implementation from FSharp.Core.
## Pros and Cons
The advantages of making this adjustment to F# are
1. Safety
2. Convenience
3. Conciseness
The disadvantages of making this adjustment to F# are the extra functions to learn.
## Extra information
Estimated cost (XS, S, M, L, XL, XXL): S to M
Related suggestions: (put links to related suggestions here)
## Affidavit (please submit!)
Please tick this by placing a cross in the box:
* [x] This is not a question (e.g. like one you might ask on [stackoverflow](http://stackoverflow.com)) and I have searched stackoverflow for discussions of this issue
* [x] I have [searched both open and closed suggestions on this site](http://github.com/fsharp/fslang-suggestions/issues) and believe this is not a duplicate
* [x] This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.
Please tick all that apply:
* [x] This is not a breaking change to the F# language design
* [x] I or my company would be willing to help implement and/or test this
## For Readers
If you would like to see this issue implemented, please click the :+1: emoji on this issue. These counts are used to generally order the suggestions by engagement.
Contributor guide
No contributing guide indexed for this repository
Research direction
No implementation files, tests, or entry points are named in the issue. Start by clarifying the API and design for the proposed try versions, then locate the relevant FSharp.Core collection implementations and tests; done requires an agreed scope and implementation plan for all listed functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100