Atif Aziz

@davidfowl Or write the help and have the C# code generated: docopt.github.io/docopt.net/dev/

Is there any project that schematizes command line help (like man pages) to make it possible to automate building strongly typed wrappers around them?

Just for fun & kicks, published an Interact Monad gist in C#, derived from fssnip.net/8ay in F# by @tomaspetricek and demonstrating an interactive computation that asks the user questions: gist.github.com/atifaziz/4a043…

5/5 Finally, in case it wasn't already obvious, Finq turns any `Func<,>` into a reader functor, monad, etc. For more, see: github.com/atifaziz/Finq

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

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: github.com/atifaziz/Finq or F(unq) + (L)inq

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. github.com/morelinq/MoreL… Okay, it was marked experimental so perhaps no one wants to go near it.

Released MoreLINQ 4.2, a minor bug fix release github.com/morelinq/MoreL…

@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: gist.github.com/atifaziz/6d147…

I've built one version of this interface using eventing - start a thread and notify on completion, and that works. Would also like to have another version that can be called from UI thread and just await async call.

Is it possible to create a new thread in C# and have it be awaited? My specific need is that need an STA thread to run the code I need to run so I can't use Task.Run() which will end up on random threads (or perhaps the Ui thread).

@dwhiteindetroit @OnurGumusDev Right, no conspiracy here. The intro microsoft.github.io/rust-for-dotne… 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.”

@OnurGumusDev I was part of the larger team on this one. They were all C# devs that had to work on a Rust project and simply wrote down their learnings to ease the next group of people who had to walk that path. No larger conspiracy or messaging than that :-)

Microsoft released a guide called Rust for .NET developers. Not sure if this is good news :) microsoft.github.io/rust-for-dotne…

@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. #gistcomment-4811260" target="_blank" rel="nofollow noopener">gist.github.com/atifaziz/8368a…

First #csadvent entry today is from @raboof: "MoreLINQ in Action" - gist.github.com/atifaziz/8368a…

@KarenPayneMVP @marcgravell And yet you get this often #discussion_r1397705842" target="_blank" rel="nofollow noopener">github.com/morelinq/MoreL… 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.

@marcgravell Agree Marc, one message I was hoping readers get from this is that copy-n-paste for this needs to be understood before using and yes in niche scenarios as you indicated that most will never need but good to have in one's toolbox if the need ever arrives.

Something I learned over the years coding is that sometimes fine tuning is not always worth getting down into the minutiae. For instance, updating values in a dictionary using code presented below which is worth the effort if performance is critical with a large dictionary yet for a small dictionary can make maintaining code troublesome for less experience team members or even the person that coded it, especially if they copied and pasted the code from the web and didn’t assert with IsNullRef.

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

Published MoreLINQ 4.1, a minor maintenance release, that primarily adds "Duplicates" and improves usability with .NET 8. github.com/morelinq/MoreL…

@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.

@KarenPayneMVP When asked as question of style then one isn't thinking about it the right way. #1 scales better syntactically: x.com/raboof/status/…

What is your style?

@k_cieslak There's “Rust for C#/.NET Developers” microsoft.github.io/rust-for-dotne… Would be neat to have F# added to the mix, though some commentary is not completely missing either: #nullability-and-optionality" target="_blank" rel="nofollow noopener">microsoft.github.io/rust-for-dotne…

MoreLINQ 4.0 is out: github.com/morelinq/MoreL… Adds pooling Batch & retires methods that are now part of .NET proper. 💯 Over 100 extensions to LINQ to Objects! 📈 50+ million downloads. 🍻 45 contributors ⚒️ Maintained over a decade (since 2009)