Igor Fedchenko

Results 37 comments of Igor Fedchenko

@Aaronontheweb Good idea, updated issue description. I did not include all the files where c# code is pasted - but included those where some important APIs are introduced (which we...

@nagytech Nice work! This would be very nice to reference tags instead of fixed line numbers. But recently @Aaronontheweb you mentioned that would be read to get rid of all...

Seems like it is more complex then just swapping types - see discussion here: https://github.com/akkadotnet/akka.net/pull/4515#discussion_r454595146 We have `Interleave` flow that actually is build from such base-to-child types flow, and it...

Well, codebase, especially such "core" part like Akka.Streams, is well-covered with tests here. I am more conserned about breaking changes here in public API... But should not be a problem...

If we need it in TestKit, I do not see any reason why not to add this reference.

Ah, that makes sense. Then to me it sounds like we are thinking of making TestKit refactoring to make it cleaner/more readable/easier to understand by other devs. If that's the...

Also, in scala they use [Sigar](https://github.com/hyperic/sigar/tree/master/bindings/dotnet) library, which seem to have bindings for .NET. @Aaronontheweb Should we port this? It will require users to have binaries of this library for...

> Do you know if that library does anything that requires elevated permissions? Can not find any particular permission requirements in related articles, seems like the most quick way is...

@Aaronontheweb found some nice samples for how to more accurately measure CPU utilization: https://github.com/dotnet/runtime/blob/4dc2ee1b5c0598ca02a69f63d03201129a3bf3f1/src/libraries/System.Private.CoreLib/src/System/Threading/PortableThreadPool.CpuUtilizationReader.Windows.cs https://github.com/dotnet/runtime/blob/4dc2ee1b5c0598ca02a69f63d03201129a3bf3f1/src/libraries/System.Private.CoreLib/src/System/Threading/PortableThreadPool.CpuUtilizationReader.Unix.cs

@Aaronontheweb So there are some small reasons to use strong naming. At least we may think they are small (depends on the number of users with that weird SN requirement)....