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
Is there anyone using other languages than C# and F# on .NET ?
I remember back then there was the #boo language but looks like it's not much used now.
Other alternative languages like #ironpython and #ironruby are either lagging a lot on supported version or abandoned apparently.
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.
Blogged a bit about discriminated unions in #csharp (yes, attributed #fsharp). Mainly to highlight some of the clever operator overloading in #aspnetminimalapi.
If you’re interested in #AWS and seeing some #JetBrainsRider demos, head over to Twitch to watch a demo by Matt Ellis. I’ll be hanging out in the chat as well.
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?
Support for resource extraction from 16-bit executables, parsing of old WinHelp files, and a couple of associated image formats (MRB, SHG, DIB) for #dotnet (written in a crazy mix of #csharp and #fsharp), all under the almighty MIT license.
I use these libraries to remake old games, but maybe others will find them useful for something, too.
I think I quite like #kotlin (at least, as far as language and tooling… jury’s still out on the larger ecosystem). It sits comfortably in-between #csharp and #fsharp, and without any of the eye-roll-inducing quirks of #rustlang.
Mayhaps I’ll keep with it for a while… maybe I’ll even do a blog post 😮 (but probably not😅).
We just shipped v2 Core Framework 2.5.0, Analyzers 1.2.0, and Visual Studio adapter 2.5.0. This release includes a bunch of quality of life improvements, bug fixes, and an overhauled assertion library that includes new assertions, new overloads, and much better (and most consistent) assertion failure messages.
I'll be trying to do a few snippets like these and see how it goes :)
Today in F# bits:
How does a web server in fsharp looks like?
It might be more familiar than you think!
Here we have two common F# web frameworks https://www.falcoframework.com https://saturnframework.org
In both cases most of what it takes is a function that can handle an http context from aspnet and return an http response!
#dotnet#csharp#fsharp developers: I'm looking for a book on .NET 5+ (more recent the better) that has the same level of depth as Jeff Richter's "Applied .NET Framework" / "CLR via C#". Subjects in there included file format of Portable Executables, garbage collector internal workings, use of stack & heap, volatile keyword & CPU caches. Is there anything out there, or is the new world solely podcasts and blog articles?
(Note: we found a bug in the fixer for the new xUnit2023 analyzer, but decided to ship this anyways because the source of the bug wasn't immediately obvious. The analyzer works fine, but the fixer always throws. Sorry about that!)
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.