docs

Regardless, those optimisations are available on the respective JITs. RyuJIT target CPU modes, breaking change due to dropping support for older hardware, https://github.com/dotnet/docs/issues/48045 > Native Image now targets x86-64-v3 architecture by default on AMD64 and provides a new -march option to specify target compatibility. Use -march=compatibility for best compatibility or -march=native for best performance if a native executable is deployed on the same machine or on a machine with the same CPU features. To list all available machine types, use -march=list. https://www.graalvm.org/release-notes/JDK_20

The intent behind these mentions was to "promote the use of Copilot" and "showcase Copilot usage scenarios in a variety of different ways". These are quotes from resolved comments in the review to a similar but slightly earlier PR[1], from the same author, to the one that introduced the specific mention referred to in the issue[2]. And that's why these suggestions to use Copilot probably don't belong in the docs: their intent was to promote a product. (To be fair, in the first comment quoted above the reviewer asks that the Copilot section be moved to the end of the document, prioritizing teaching the user about the actual feature the article was about). One additional problem, already pointed out by others, is that Copilot seems to be the only AI tool showcased in the docs. Besides suggesting the intent of these suggestions is purely pro

Certain parts of Microsoft Learn are permissive, most .NET/C# documentation is Creative Commons Attribution: * Conceptual docs: https://github.com/dotnet/docs * BCL: https://github.com/dotnet/dotnet-api-docs * ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs * WinForms/WPF: https://github.com/dotnet/docs-desktop The C# language specification is unfortunately a bit fuzzier, but the conceptual docs above include what most people want: 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

MS docs ar now on github. Licence lists "CC-BY-4 and MIT licence found" https://github.com/dotnet/docs/tree/main Yeah, I saw that devdocs and the like don't include what was previously not cross platform and not popular for linux guys: C#, msbuild.

could you clone the docs repo? https://github.com/dotnet/docs

You might be able to do something with this: https://github.com/dotnet/docs The browsy bits might not work without a server (not sure), but the documents themselves are markdown.

You can use named pipes without WCF[0]. Sample here[1]. I've also used the IpcServiceFramework[2] before, and it worked a treat. [0] https://github.com/dotnet/docs/blob/master/docs/standard/io/... [1] https://github.com/GustavoHennig/PipePoc [2] https://github.com/jacqueskang/IpcServiceFramework

It already has. [0] [0] https://github.com/dotnet/docs/pull/2706/files

That's not quite correct. More is collected, but the docs are still being updated. [0] The other things being collected are: * Geographical location * Operating system and version [0] https://github.com/dotnet/docs/pull/2706/files

Have you by any chance seen that I specifically mentioned version 7 of C#? Which allows full control how async/await works, kind of like on the upcoming C++ co-routines, where async/await become syntactic sugar for blessed data structure. EDIT: Should have provided the actual information. The feature as introduced in C# 7 is called "Generalized async return types". https://github.com/dotnet/docs/issues/1756

That's a typo! Thanks, I'll get that fixed. PR out here: https://github.com/dotnet/docs/pull/1584

You can use the schema to figure out the valid values and descriptions for some of the values, so that might help. I agree that a technical reference would probably help since reading the schema isn't fun. Doesn't shock me that it's mostly GitHub search since most of our docs are hosted on GH: https://github.com/aspnet/Docs https://github.com/dotnet/docs You can always add a request to the docs UserVoice: https://msdocs.uservoice.com/forums/364242-general-site-feed... Azure also has its own docs UserVoice: https://feedback.azure.com/forums/217534-documentation