.NET 7 미리보기 1의 새로운 기능 [WIP]

dimohy · 2월 6, 2022, 2:24오전

.NET 7 미리보기 1의 새로운 내용이 채워지고 있네요.

Microsoft.Extensions에 지속적인 Nullable 주석 추가
추적 API를 지속적으로 개선
CodeGen 관련 개선
P/Invoke 소스 생성
System.Text.Json의 새로운 API 추가
Mono의 핫 다시로드 개선

github.com/dotnet/core

What's new in .NET 7 Preview 1 [WIP]

opened 06:36PM - 11 Jan 22 UTC

closed 07:25PM - 24 Jan 23 UTC

leecow

documentation

# What's new in .NET 7 Preview 1 This issue is for teams to highlight work fo…r the community that will release .NET 7 Preview 1 To add content, use a new conversation entry. The entry should include the team name and feature title as the first line as shown in the template below. ``` ## Team Name: Feature title [link to the tracking issue or epic item for the work] Tell the story of the feature and anything the community should pay particular attention to be successful using the feature. ``` Preview 1: https://github.com/dotnet/core/issues/7106 Preview 2: https://github.com/dotnet/core/issues/7107 Preview 3: https://github.com/dotnet/core/issues/7108 Preview 4: https://github.com/dotnet/core/issues/7378 Preview 5: https://github.com/dotnet/core/issues/7441 Preview 6: https://github.com/dotnet/core/issues/7454 Preview 7: https://github.com/dotnet/core/issues/7455

LightEach · 2월 6, 2022, 8:35오전

아니 무슨 닷넷7이 벌써나와…

rkttu · 2월 7, 2022, 2:37오후

익히 알려진대로 이제 1년에 한 번씩 메이저 릴리스가 나옵니다. 닷넷 6가 이번에 나왔으니 2년 뒤에 새 LTS 버전인 닷넷 8이 2023년이 나오게 됩니다.

dimohy · 2월 13, 2022, 5:46오전

새로운 정규식 소스생성기 소개

github.com/dotnet/runtime

Developers can precompile their Regex code for faster startup

opened 01:19AM - 14 Nov 20 UTC

closed 11:53PM - 13 Dec 21 UTC

danmoseley

area-System.Text.RegularExpressions User Story Priority:2 Cost:M Team:Libraries

[AB#1255830](https://devdiv.visualstudio.com/10e66e43-9645-4201-b128-0fdc3769cc1…7/_workitems/edit/1255830) Regex has an interpreted mode and a compiled mode. The compiled mode takes longer to start, but is generally faster. Some users want both startup time and performance; other users want to run on a platform where JITted code is not allowed, and also want performance. For those users, .NET Framework allowed the generated code to be saved out but .NET Core/.NET 5 does [not plan to support saving emitted IL](https://github.com/dotnet/runtime/issues/15704). Instead, we could develop a [Roslyn Source Generator](https://devblogs.microsoft.com/dotnet/introducing-c-source-generators/) that would generate the necessary code (as C#) at compile time. Essentially API should be need on Regex, as the generated code would hook into it in the regular way, by deriving from RegexRunner and implementing FindFirstChar() and Go(). This API is all public/protected today (indeed it happens that .NET Core can load regexes written out by .NET Framework.) TBD the user experience - eg., how one must annotate regexes in order to trigger the generator - assuming it doesn't attempt to read all the code to try to infer them - and how the generated code is wired up. For example, one could imagine requiring an annotation like this (we could also expose API on the source generator so it could consume a list of regexes, for example) ``` [RegexSourceGenerator(“(?:[0-9]{1,3}\.){3}[0-9]{1,3}”, RegexOptions.IgnoreCase)] public partial Regex CreateIpAddressRegex(); ``` This new attribute would need to be exposed somewhere, probably on the Regex assembly since the code being compiled would be referencing that anyway. Also TBD the implementation details necessary to wire into the existing Regex implementation - this is probably most of the work. cc @pgovind @eerhardt @stephentoub this is just a summary of our email thread. Anything to add? In terms of customers, we have at least one major 1st party service that heavily uses regex and highly values both throughput and startup time. This is probably P1 for them. @danroth27 in a Blazor app, can I assume that most users in the .NET 6 timeframe will be content with either using Javascript regexes, or interpreted mode .NET regexes? In my mind this is P2/P3. @marek-safar similar question for Xamarin, on platforms that don't JIT, Xamarin apps presumably currently interpret the ref-emitted code, or use the regex interpreted mode - and this would not be a big win for them - we had talked about P2.