I came up with a thing in #fsharp today and I am unsure about it. I don't know if it's cute, useless, or useful; I cannot see far enough ahead to understand its implications.
type ErrExn = | Err of DomainError | Exn of System.Exception
This DU unifies domain errors (that are represented in a user-written DU) and exceptions.
I'd expect it to be in a function with a signature of 'a -> Result<'b, ErrExn>.
I don't know if this gives value over separate domain errors and exceptions.
We just shipped v2 Core Framework 2.8.0, Analyzers 1.13.0, and Visual Studio adapter 2.8.0. The primary purpose of this release is a new parallelism algorithm that should make test timing more reliable, and make thread deadlocks in your tests less likely.
In one hand I feel sad that some lovely folks on F# twitter were laid out or their teams were disbanded, on the other hand, I feel that there's certain momentum in the F# community as I see more and more folks getting to try it out and talk about it, perhaps that ocaml popularity boom helped a lot here as well.
We just shipped v2 Core Framework 2.7.1, Analyzers 1.12.0, and Visual Studio adapter 2.5.8. This includes a few new assertion overloads, four new #Roslyn analyzers (and two new suppressors), and a handful of bug fixes.
I want to see if it's possible to replace runtime reflection in @xunit v3 with #Roslyn source generators (for better performance and to support NativeAOT), but I think I've already hit the first blocking point: no support for #FSharp? Only #CSharp and #VB? #dotnet
What's your #editor / #IDE of choice, and why is it so? Do you use that for all tasks and #programming languages, or do you switch between editors depending on what you're working on?
I mostly use #IntelliJ / #Goland for large projects, and #VSCode for simpler ones. But tbh, I find myself increasingly using VS Code even for projects where I'd previously would reach for IntelliJ. And their poor story around language server integrations makes them feel less relevant today than they used to be.
@anderseknert I usually end up using VS Code, as it has by far the best experience for #fsharp using the #Ionide plugin. I keep trying to do more in Rider, which also has some great features, but I always end up missing Ionide. I end up using VS Code for most other things too. The ease of creating custom workspaces with different settings and plugins, and the integrated terminal help a lot. I recently got a pretty good workflow going for doing presentation slides in it using Pandoc.
For real, whoever is saying that F# or OCaml require a PhD in Math or are languages just for math, science, and academic stuff is completely lying to you, it is no harder than learning JavaScript/python or any other language out there.
Let's talk about Fable, an efficient and productive F# to JavaScript compiler with easy interop to JavaScript code. Discover how F# can benefit your app development! #Fable#FSharp
On a random walk, I bumped into F#. Sounds interesting... tell me more!
My word... every search for "qucik start" or "tutorial" leads down an academic rabbit hole of type definitions and other associated lunacy.
Honestly, just show me how you do a few things. You don't like loops? Fine. You don't like variables? Fine. Show me how you solve this problem that way. Too much to ask?
We just shipped v2 Core Framework 2.6.6 and Analyzers 1.10.0. The core framework update adds assembly-level BeforeAfterTest support, as well as eliminating false security warnings related to old packages from .NET Standard 1.x. We've also added two new analyzers and fixed issues in a few more.
We just shipped v2 Core Framework 2.6.5 and Analyzers 1.9.0. The core framework updates TheoryData<T> for easier usage, and we've added two new analyzers (in addition to fixing and few bugs).
We just shipped v2 Core Framework 2.6.4, Analyzers 1.8.0, and Visual Studio adapter 2.5.6. This release is primary a bug fix release, but does include reintroduction of support for VS2019 16.11+ for the analyzers project.
Going through some #fsharp#dotnet 8 demos for the latest #JetBrainsRider release party, and wowza, this was a great release for #fsharp folks. So much good stuff.