SLIMA
csharplang
SLIMA | csharplang | |
---|---|---|
4 | 262 | |
63 | 10,899 | |
- | 1.1% | |
3.6 | 9.6 | |
10 months ago | 5 days ago | |
CoffeeScript | C# | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SLIMA
-
What is to go-to environment on Windows for Common LISP development?
Careful! The Atom plugin is SLIMA, since a few years: https://github.com/neil-lindquist/SLIMA/ (it's a fork, atom-slime's maintainer didn't feel like sharing commit rights). In doubt: https://lispcookbook.github.io/cl-cookbook/editor-support.html
-
Slima for Atom: Quote doesn't evaluate properly
https://github.com/neil-lindquist/SLIMA/issues would probably like to know about that.
- Hell Is Other REPLs
-
VS Code
You can also change to Atom and use SLIMA ( https://github.com/neil-lindquist/SLIMA ), which may offer an easier transition than VS Code -> Emacs.
csharplang
- Discriminated Unions: Essa feature faz falta no CSharp
-
DevDocs
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
-
The golden age of Kotlin and its uncertain future
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
-
When static types make your code shorter
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.
-
.NET 8 – .NET Blog
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]) { ... }
-
What's new in C# 12: overview
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...)
-
Robust Design through Value Objects in C#
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.
-
The combined power of F# and C#
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)
-
Should i quit Django and move to asp.net
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.
- Can constructor parameter assignment be made less verbose?