csharplang VS DapperQueryBuilder

Certain parts of Microsoft Learn are permissive, for example the .NET BCL documentation is Creative Commons Attribution: https://github.com/dotnet/dotnet-api-docs as is ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs (a good hint if documentation is permissively licensed and on GitHub is if there's an edit button at the top.)

The C# language specification is unfortunately a bit fuzzier: https://github.com/dotnet/csharplang/discussions/4855

The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard

No OP, but for example you still see the C# folks still struggling to add discriminated unions to the language because of complex interactions due to its too many features[1]. Virtual threads are easier to use than async/await is another example.

[1] https://github.com/dotnet/csharplang/issues/113

For example, C# had a research fork called Spec# that had compile-time support for contracts, with keywords such as requires (for arguments) and ensures (for return values), all the way back in 2004. While still being discussed, it doesn't seem to be shipping any time soon.

Hi there. I'm the language designer who created the 'Collection Expression' design/specification: https://github.com/dotnet/csharplang/issues/5354

You can see the entire history of the proposal there. To answer you specific question, we went with `..` because that's what the language already uses for the complimentary 'pattern matching deconstruction' form for collection patterns.

In other words, you can already say this today:

    if (x is [var start, .. var middle, .. var end]) { ... }

You must specify concrete type.

There was a plan to have "natural type" so "var list = [1,2,3]" would be of type "List" but it was postponed to C# 13 (https://github.com/dotnet/csharplang/issues/5354#issuecommen...)

While C# currently lacks direct support for this kind of functionality, there's a glimmer of hope with an active proposal under discussion that aims to bring this feature to the language. This potential addition promises a future where C# can natively offer similar robust type narrowing.

Given few people anticipated ValueTuple and C# adding a more direct tuple syntax, I feel like it is only a matter of time before C# adds discriminated unions.

(There are multiple proposals tracking the idea. This seems the most comprehensive and "central": https://github.com/dotnet/csharplang/issues/7016)

I always liked list abbreviations in python, but I absolutely love Linq. I believe there is a feature proposal for C# 12, which makes collection initialization better imo.

When I first drafted this idea of concatenating FormattableStrings to build SQL, I didn't have any ambition to inherit from FormattableString, then in this new project (aimed at writing something more flexible/reusable and less coupled with Dapper) I realized that I was basically writing what you said - a mutable FormattableString. But yeah, when I rely on this new structure for SQL-Building I should pay extra attention to those risks.

How does this compare to Dapper Query Builder?

Yo! Love this library, makes it real easy to put together params for procs. Any headway on Issue #27? I've got a workaround but would love to be able to use multiple result sets natively.

My ideal vision is some higher level library that provides the DSL and parsing, and provides a way to either output Expressions for use with IQueryables or some other implementation to inject it into hand-written SQL queries. I have no clue if such a thing is even possible. I've found Sieve and DapperQueryBuilder. It seems like DapperQueryBuilder would support such a use case, using the Fluent API and conditionally adding Selects, Order By, Where, etc. Have you explored something similar? What did you find?

This project is just a fork of another QueryBuilder that I made for Dapper where manually building queries is much more important (as compared to EF where most queries will be made using LINQ expressions - I know).

LOL. Just a bored developer who saw an opportunity. :-) When I posted a few days ago about DapperQueryBuilder someone suggested that this same FormattableString-hacking could be used for Logging libraries. Since the major parts of processing FormattableString are identical (same regex, same loops, etc) and since I was a little bored this weekend I decided to try out this idea :-)