Tomas Grosup
Tomas Grosup
I think this is a viable approach. 1. A micro-optimization PR which does not fix nor change anything, only makes it faster 2. Bugfixes with added tests (failing before, success...
Iterators => interceptors ?
I came here to share the perspective of 'minority-languages-on-dotnet' (and to link this to an issue where I am collecting use cases exactly like this one :-) ): Maybe not...
1. The APIs which can fail on non-null values ( choice,choices,sample with collections that are emty/too small) -> I would favour having a try* variant of them, to avoid developers...
@reinux : I am still thinking of a better self-explainable API, I don't think a tuple of 3 with same types is best. Even though the ordering (previous,match,next) is likely...
(See AzDo message above, was not mergeable and contains no diff)
Is it about removing the https://github.com/dotnet/netcorecli-fsc project and all references to it? And therefore not making `