Atif Aziz

[Atif Aziz @raboof]

It's just been crickets here since a minute! 💤 Time to try & change that (soon).

[Atif Aziz @raboof]

@davidfowl Or write the help and have the C# code generated: https://t.co/kr2GHw7Pnl

[Atif Aziz @raboof]

Just for fun & kicks, published an Interact Monad gist in C#, derived from https://t.co/UMrFuLGp4b in F# by
@tomaspetricek and demonstrating an interactive computation that asks the user questions:
https://t.co/NCuPsOAZzu

[Atif Aziz @raboof]

5/5 Finally, in case it wasn't already obvious, Finq turns any `Func<,>` into a reader functor, monad, etc.

For more, see: https://t.co/g1LrFn6Q3r

[Atif Aziz @raboof]

1/5 Here's a (peculiar) idea…writing & combining C# functions (`Func<,>`) entirely with LINQ, as if you didn't have `=>` in the language. Introducing Finq: https://t.co/g1LrFn6Q3r or F(unq) + (L)inq

[Atif Aziz @raboof]

4/5 Finq can also give you fallible functions naturally by just using the `where` clause from LINQ:

[Atif Aziz @raboof]

The fact that it fixes one crucial bug in (async) Merge that you're bound to encounter in simple use cases & yet no one reported it says a lot about how many people are using it. https://t.co/snsbdZy9CM Okay, it was marked experimental so perhaps no one wants to go near it.

[Atif Aziz @raboof]

Released MoreLINQ 4.2, a minor bug fix release https://t.co/6e8phwQLak

[Atif Aziz @raboof]

@RickStrahl Use Thread with TaskCompletionSource for signaling + Task? Seems to be cleanest & simplest way I can think of right now. As a Gist for prosperity: https://t.co/BqHcI5woRq

[Atif Aziz @raboof]

@dwhiteindetroit @OnurGumusDev Right, no conspiracy here. The intro https://t.co/tmkVvXKM99 says too “…authors of this guide were themselves C#/.NET developers who were completely new to Rust. This guide is the compilation of the knowledge acquired…writing Rust code over the course of several months.”

[Atif Aziz @raboof]

@CsAdvent “…great demo, thanks for taking the time to put it together…some of the more esoteric MoreLINQ operators (had never really considered…, but seeing how they're used here makes me realise they fit some scenarios I've seen before)…” & this made my day. https://t.co/gw8hqpb0n4

[C# Advent @CsAdvent]

First #csadvent entry today is from @raboof: "MoreLINQ in Action" - https://t.co/Lmex1nCVp6

[Atif Aziz @raboof]

@KarenPayneMVP @marcgravell And yet you get this often https://t.co/NCDmcEPDkx perhaps because the .NET team sweats over this stuff & talks about all the ways they got the perf improvements, everyone feels now they need to sweat it to too.

[Atif Aziz @raboof]

Didn't know what to post so for whatever it's worth, this is my #GitHubUnwrapped! ¯\_(ツ)_/¯ Get your own: https://t.co/EdrRJMz8Ci

[Atif Aziz @raboof]

Published MoreLINQ 4.1, a minor maintenance release, that primarily adds "Duplicates" and improves usability with .NET 8. https://t.co/viQRgbRnLV

[Atif Aziz @raboof]

@SimonCropp Ouch. Though the assumption is fair unless it causes side-effects and if it does, then it should be an IEnumerator. Alas, not enough folks take care to make the distinction.

[Atif Aziz @raboof]

@KarenPayneMVP When asked as question of style then one isn't thinking about it the right way. #1 scales better syntactically: https://t.co/gI290MuMLk

[Atif Aziz @raboof]

3/5 I find many seasoned C# devs still say that choosing between LINQ's query syntax & chaining backing methods is a question of style & preference, but the latter doesn't scale as computational expressions get justifiably long; chaining gets ugly & deteriorates into a mess.

[Atif Aziz @raboof]

@k_cieslak There's “Rust for C#/.NET Developers” https://t.co/LXNReAAGzm Would be neat to have F# added to the mix, though some commentary is not completely missing either: https://t.co/JDYktzRBwX