Konto erstellenAnmelden

Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Only available when logged in.
troet.cafe ist Teil eines dezentralisierten sozialen Netzwerks, angetrieben von Mastodon.
Hallo im troet.cafe! Dies ist die derzeit größte deutschsprachige Mastodon Instanz zum tröten, neue Leute kennenlernen, sich auszutauschen und Spaß zu haben.

Verwaltet von:

Serverstatistik:

7,1 Tsd.
aktive Profile
Mehr erfahren

troet.cafe: ÜberProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.2.19

#csharp

47 Beiträge34 Beteiligte3 Beiträge heute
Edaqa Mortoray

I find C#'s features to always somehow be incomplete. For example, I can declare a class without a constructor, like below, and use new HandInfo{... to create with names. However, it doesn't work nullable: enable, thus I have to revert back to manually creating a constructor.

#csharp
D. Moonfire

Played a few hours of Palworld with Child.0.

Also worked on my C# CLI parsing library. Mostly I worked out some ideas and patterns to make sure they fit. One implementation I'm doing is based on C#'s XElement pattern:

var root = new ComponentCliCommand(
  new ValueCliOption<string>("option"),
  new ValueCliOption<int>('n', "number"),
  new SwitchCliOption("help"),
  new CliHandler(_ => Console.WriteLine("I ran a command!"));

Since the entire purpose is to make this DI-friendly and also Autofac-module friendly, all of the classes and subclasses can be extended and then added into the service provider.

public RootCommand(IEnumerable<IMyLocalVerbs> verbList, CurrentDateOption currentDateOption)
  : base(currentDateOption)
{
  this.AddRange(verbList);
}

So far, the pattern seems "reasonable"?

I can also easily convert a reflection-based version of the command and convert them into components, which would let me do a CommandLineParser-style command object. And the handler (CliHandler) doesn't have to be in the same class (though I prefer it does).

#CSharp
Felix Palmen :freebsd: :c64:

Today, I implemented the #async / #await pattern (as known from #csharp and meanwhile quite some other languages) ...

... in good old #C! 😎

Well, at least sort of.

* It requires some standard library support, namely #POSIX user context switching with #getcontext and friends, which was deprecated in POSIX-1.2008. But it's still available on many systems, including #FreeBSD, #NetBSD, #Linux (with #glibc). It's NOT available e.g. on #OpenBSD, or Linux with some alternative libc.

* I can't do anything about the basic language syntax, so some boilerplate comes with using it.

* It has some overhead (room for extra stacks, even extra syscalls as getcontext unfortunately also always saves/restores the signal mask)

But then ... async/await in C! 🥳

Here are the docs:
zirias.github.io/poser/api/lat

zirias.github.ioposer: PSC_AsyncTask Class Reference
#coding
Chris Woody Woodruff

Week 1 of learning Rust as a C# dev:

Fewer keywords. Stricter rules. More thinking.
Rust’s minimalism doesn’t just simplify, it reshapes how you code.

Here are my takeaways from the first 7 days:
woodruff.dev/reflections-on-we

Chris Woody Woodruff · Reflections on Week 1: Rust's Minimalism Hits Different - Chris Woody WoodruffSeven days into learning Rust, and I feel like I’ve been through a developer bootcamp with a compiler that doubles as a personal trainer. It doesn’t let you slack, but it does make you better. This week, I went from installing the toolchain to wrestling with immutable variables and puzzling over semicolons in return statements. As a C# developer, I expected syntax differences, but I didn’t expect the philosophical shifts. Let’s recap what stood out, what stung, and why I’m still excited to keep going.
#RustLang#CSharp#DotNet
Chris Woody Woodruff

I'm learning Rust from a C# developer's perspective—one day at a time for 42 days.

I have 36 days left.

If you're curious how Rust stacks up against .NET, follow along here:
woodruff.dev/from-c-to-rust-a-

Chris Woody Woodruff · From C# to Rust: A 42-Day Developer Challenge - Chris Woody WoodruffI’ve spent over a decade writing C# and building solutions on .NET. But for six weeks, we will step outside the managed world of garbage collection and runtime JIT to dive headfirst into Rust—a systems programming language that promises performance, safety, and no nulls. Over the course of 42 days, we will learn something new about Rust every single day. We will fight the borrow checker. We will make mistakes. And I will blog it all from the perspective of a C# developer trying to make sense of it.
#RustLang#CSharp#DotNet
*
bitbonk

SpacetimeDB is an interesting new type of relational database that I haven't quite wrapped my head around yet.

It is designed for real time massive multiplayer games and uses some sort event sourcing (CRDTs?) but has many more potential use cases than just games.

It works particularly well with .NET and C#. So I have cleaned up and simplified the C# quickstart sample.

github.com/bitbonk/spacetime-q

A quickstart chat demo for SpacetimeDB. Contribute to bitbonk/spacetime-quickstart-chat development by creating an account on GitHub.
GitHubGitHub - bitbonk/spacetime-quickstart-chat: A quickstart chat demo for SpacetimeDBA quickstart chat demo for SpacetimeDB. Contribute to bitbonk/spacetime-quickstart-chat development by creating an account on GitHub.
#spacetimedb#sql#dotnet
*
Chris Woody Woodruff

Day 6 of learning Rust as a C# dev:
No classes. No objects. Just tuples, arrays, and a compiler that keeps you honest.

Rust’s types feel simple until they don’t.

Here’s what I learned:
woodruff.dev/rust-scalar-and-c

Chris Woody Woodruff · Rust Scalar and Compound Types: Where Are My C# Classes? - Chris Woody WoodruffWhen I first started exploring Rust, one of my instincts was to reach for a class. You know the drill. Need to model some data? Write a class, slap a few properties on it, and maybe add a constructor or two. But Rust had other plans. On Day 6, I dug into Rust’s scalar and compound types and quickly realized that Rust doesn’t want you to start with classes. Instead, it hands you a small set of powerful primitives and says, “Let’s build something lean.”
#RustLang#CSharp#DotNet
Chris Woody Woodruff

Day 5 of learning Rust as a C# dev:

Functions look familiar... until they don’t.

No return keyword, types after names, and the last line does the returning?

It’s weird. It’s clean. I kind of love it.

woodruff.dev/functions-in-rust

Chris Woody Woodruff · Functions in Rust: Familiar Yet Different - Chris Woody WoodruffToday’s Rust lesson hit a familiar note but with a twist. Writing functions in Rust feels almost like writing them in C#. Until, of course, the compiler reminds you that this language doesn’t always play by the same rules. On Day 5 of my Rust-for-C# developers journey, let’s break down function definitions, type inference, return values, and where Rust and C# shake hands... and where they give each other a suspicious side-eye. On Day 5 of my Rust-for-C# developers journey, let’s break down function definitions, type inference, return values, and where Rust and C# shake hands... and where they give each other a suspicious side-eye.
#RustLang#CSharp#DotNet
EntdeckenLive-Feeds
Über