bflat
CoreCLR
bflat | CoreCLR | |
---|---|---|
27 | 22 | |
3,474 | 12,786 | |
0.7% | - | |
6.9 | 0.0 | |
about 2 months ago | over 1 year ago | |
C# | ||
GNU Affero General Public License v3.0 | - |
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.
bflat
-
Borgo is a statically typed language that compiles to Go
The sibling pretty much sums it up. But if you want more detail, read on:
Generally, there are three publishing options that each make sense depending on scenario:
JIT + host runtime: by definition portable, includes slim launcher executable for convenience, the platform for which can be specified with e.g. -r osx-arm64[0].
JIT + self-contained runtime: this includes IL assemblies and runtime together, either within a single file or otherwise (so it looks like AOT, just one bin/exe). These requires specifying RID, like in the previous option.
AOT: statically linked native binary, cross-OS compilation is not supported officially[1] because macOS is painful in general, and Windows<->Linux/FreeBSD is a configuration nightmare - IL AOT Compiler depends on Clang or MSVC and a native linker so it is subject to restrictions of those as a start. But it can be done and there are alternate, more focused toolchains, that offer it, like Bflat[1].
If you just want a hello world AOT application, then the shortest path to that is `dotnet new console --aot && dotnet publish -o {folder}`.
[0] https://learn.microsoft.com/en-us/dotnet/core/rid-catalog
[1] https://github.com/bflattened/bflat (can also build UEFI binaries, lol)
-
Learn how to build beautiful and interactive .NET command-line applications using System.CommandLine and Spectre.Console with my latest blog post
See here
-
Question about NativeAOT platform support
See B flat
-
Native AOT Overview
I've been wondering how to integrate modern .NET Core into a custom build system (buck2) and was wondering similar things. There's this project I think is cool called bflat[1] that basically makes the C# compiler more like the Go compiler in the sense it's a one-shot single-use tool that can cross compile binaries natively. It's done by one of the people on the .NET Runtime team as a side project, but quite neat.
I think in practice you're supposed to compile whole .dll's or assemblies all at once, which acts as the unit of compilation; I don't think the csharp compiler generates native object-files-for-every-.cs, the kind of approach you'd expect from javac or g++. Someone please correct me if I'm wrong though! I'd like to learn more about this.
[1] https://github.com/bflattened/bflat
-
If you were stuck on a remote island, would you pick C# as your programming language
You can compile without a GC using https://github.com/bflattened/bflat
- AOT
-
Hey people, made a game for my CS homework as a freshman using C#, what do you guys think about it?
nice. have you tried compile it using https://github.com/bflattened/bflat to have native executable? as long as you don't have PackgeReference it can be compiled using bflat instead of full dotnet
- Bflat – a single ahead of time crosscompiler and runtime for C#
-
bflat - Build native C# applications independent of .NET
The creator actually addresses this issue:
CoreCLR
-
The Performance Impact of C++'s `final` Keyword
Yes, that is true. I'm not sure about JVM implementation details but the reason the comment says "virtual and interface" calls is to outline the difference. Virtual calls in .NET are sufficiently close[0] to virtual calls in C++. Interface calls, however, are coded differently[1].
Also you are correct - virtual calls are not terribly expensive, but they encroach on ever limited* CPU resources like indirect jump and load predictors and, as noted in parent comments, block inlining, which is highly undesirable for small and frequently called methods, particularly when they are in a loop.
* through great effort of our industry to take back whatever performance wins each generation brings with even more abstractions that fail to improve our productivity
[0] https://github.com/dotnet/coreclr/blob/4895a06c/src/vm/amd64...
[1] https://github.com/dotnet/runtime/blob/main/docs/design/core... (mind you, the text was initially written 18 ago, wow)
- How are stack machines optimized?
-
Best .net/c# resources for senior engineer
Sort of, some topic are not relevant anymore, consider this - https://github.com/dotnet/coreclr/tree/master/Documentation/botr
-
Is there a C# under the hood tutorial?
Fairly advanced stuff but the Book Of The Runtime (BOTR) it's a invaluable resource
-
In depth learning of C#?
After that you can check out the The Book of the Runtime, which is the CoreCLR version of the previous book.
-
.NET 6 is now in Ubuntu 22.04
Technically the restrictions already exist, just as a part of the development experience.
- .NET Hot Reload is only implemented on Windows. It requires support in the .NET runtime, which is technically possible to implement, but the team has not gotten around to implementing it for years. This doesn't have to do with the issue around MS removing the "dotnet watch" command, it's for the "Edit and Continue" feature in IDEs.[1][2]
- MS was considering deprecating Omnisharp, the open-source language server that implements C# support for VS Code, and replacing it with a closed-source version. Since the announcement, commits to omnisharp-vscode have dropped off significantly. The lack of Omnisharp would mean there would be no real open-source C# development environment for Linux anymore, since MonoDevelop was abandoned a few years ago. [3]
[1] https://youtrack.jetbrains.com/issue/RIDER-31366/EditContinu...
[2] https://github.com/dotnet/coreclr/issues/23685
[3] https://github.com/omnisharp/omnisharp-vscode/issues/5276
-
what a .NET specialist should know
The next step is to realize everything you think you know about .NET is just an abstraction. Next step is to learn about what is going on behind all that syntax sugar and facades. 1st step might be https://github.com/dotnet/coreclr/tree/master/Documentation/botr then go down the rabbit hole and have fun
- Trouble with random numbers
-
Is CLR via C# still good?
Book of the Runtime
-
Understanding dotnet
As for the books, back in the days I really enjoyed reading “CLR via C#" by Jeffrey Richter which helped a lot to understand what is under the hood. Other from that, try The Book of the Runtime
What are some alternatives?
asdf-dotnet-core - ✨ .Net Core plugin for asdf version manager
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
zerosharp - Demo of the potential of C# for systems programming with the .NET native ahead-of-time compilation technology.
sdk - Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
dmd - dmd D Programming Language compiler
referencesource - Source from the Microsoft .NET Reference Source that represent a subset of the .NET Framework
centos-stream
AspNetCore-Developer-Roadmap - Roadmap to becoming an ASP.NET Core developer in 2024
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
Windows UI Library - Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications