z
Size: a a a
2020 July 14
GL
Там еще описывается почему иногда выгодно переписывать C/С++ блоки на C#, т. е. почему менеджед языки дают пососать унменеджед языкам. Здесь недавно кто-то срал себе в штаны и говорил, что это невозможно, что аот будет всегда лучше жит
GL
А ну ка покажи где
In this release, we’ve continued, and even accelerated, the process of porting native implementations in the coreclr runtime from C/C++ to instead be normal C# managed code in System.Private.Corelib. Such a move has a plethora of benefits, including making it much easier for us to share a single implementation across multiple runtimes (like coreclr and mono), and even making it easier for us to evolve API surface area, such as by reusing the same logic to handle both arrays and spans.
GL
Ctrl+F и читай с этого места
SR
твоим инструментом будет редактор кода, в этой проге ты пишешь свой код
вим
z
George Lewinsky
In this release, we’ve continued, and even accelerated, the process of porting native implementations in the coreclr runtime from C/C++ to instead be normal C# managed code in System.Private.Corelib. Such a move has a plethora of benefits, including making it much easier for us to share a single implementation across multiple runtimes (like coreclr and mono), and even making it easier for us to evolve API surface area, such as by reusing the same logic to handle both arrays and spans.
Ну это ваще ДРУГОЕ
GL
У них был миксед C/C++/C#, ясен красен там просадки, т.к бридж не оптимизирован
Про просадки там дальше:
but if a thread is currently executing C/C++ code in the runtime, the GC may need to wait until that call completes before it’s able to suspend the thread. Thus, the more work we can do in managed code instead of native code, the better off we are for GC pause times. We can use the same Array.Sort example to see this. Consider this program:
but if a thread is currently executing C/C++ code in the runtime, the GC may need to wait until that call completes before it’s able to suspend the thread. Thus, the more work we can do in managed code instead of native code, the better off we are for GC pause times. We can use the same Array.Sort example to see this. Consider this program:
z
George Lewinsky
Про просадки там дальше:
but if a thread is currently executing C/C++ code in the runtime, the GC may need to wait until that call completes before it’s able to suspend the thread. Thus, the more work we can do in managed code instead of native code, the better off we are for GC pause times. We can use the same Array.Sort example to see this. Consider this program:
but if a thread is currently executing C/C++ code in the runtime, the GC may need to wait until that call completes before it’s able to suspend the thread. Thus, the more work we can do in managed code instead of native code, the better off we are for GC pause times. We can use the same Array.Sort example to see this. Consider this program:
> т.к бридж не оптимизирован
GL
ну, а выше не про это
