ply
FsToolkit.ErrorHandling
Our great sponsors
ply | FsToolkit.ErrorHandling | |
---|---|---|
3 | 10 | |
242 | 440 | |
-0.4% | - | |
0.0 | 8.5 | |
over 1 year ago | about 1 month ago | |
F# | F# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ply
-
I have created a library for F# that is inspired ZIO and Cats Effects for Scala. It takes advantage of fibers for making scalable and efficient concurrent programs. I thought some people here might be interested in it!
I work with mass-scale concurrency using green threads (~50000 server tasks a second, as many threads at a time as possible, ~50ms latency differences matter). How is the performance relative to something like Ply? I am particularly concerned with GC pauses.
-
FsToolkit.ErrorHandling 2.2.0 🚀
Ply is a great library for interacting with Tasks: https://github.com/crowded/ply
-
Making Http Requests in F#
DISCLAIMER: I'll be using Ply in most of the samples due to it's efficient task CE and the easy interoperability between C# tasks as well as F#'s async. Http operations are by nature async operations, that means using async/await in C#/JavaScript or using async {} in F# which can be a little annoying when you need to append |> Async.AwaitTask to every function/method that returns a Task.
FsToolkit.ErrorHandling
-
It seems like I'm forced to make this choice at least once a day
I do think at least some of FSToolkit.ErrorHandling should be part of the core library though, it has nearly everything you could want for using these types.
-
F# 6 Hopes and kind of a rant
Monad stacks, most commonly Async>, require a lot of boilerplate to deal with or using something like https://github.com/demystifyfp/FsToolkit.ErrorHandling . Which is fine, but it causes dependency mismatches between libs or type mismatches as everyone is implementing their own. A language solution would be nice...
- FsToolkit.ErrorHandling 2.2.0 🚀
-
Say hello to "block" - the recently finalized name for the upcoming immutable array type
This library is nice: https://github.com/demystifyfp/FsToolkit.ErrorHandling
What are some alternatives?
visualfsharp - The Visual F# compiler and tools
FSharp.SystemTextJson - System.Text.Json extensions for F# types
FSharp.CosmosDb - An F# wrapper around Cosmos DB's .NET SDK to make it more friendly for F# developers
Npgsql.FSharp - Thin F# wrapper around Npgsql, the PostgreSQL database driver for .NET
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
FsHttp - A lightweight F# HTTP library by @SchlenkR and @dawedawe
ClosedXML.SimpleSheets - Easily generate Excel sheets from F#
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
fio - :wrench: A type-safe, highly concurrent library for F# based on pure functional programming
Optional - A robust option type for C#
fslang-suggestions - The place to make suggestions, discuss and vote on F# language and core library features