Andrei Andreev

+1

Current issues: - [x] Infinity representation in Decimal is weird, as it uses a e9e15 number. This produces incorrect results on unary operations (like exp or log10). Solution: Represent non-finite...

Would like to pick up some of these? I'm going to fix the infinity one at least

Good news: most of the broken tests were non-finite-values-related **\*proceeds with fixing infinity on master\*** 

I would suggest grabbing hyperbolic functions since I have no idea how they work %) I'll probably do something with the rounding issue

Hey WooshiiDev > same active state 👍 > Selection only toggles 👍 > Depth-only toggling 👍 Looks good to me!

I think it doesn't even matter how it's implemented - like in Zenject, or just `Container.Validate()` which we would need to call ourselves and which throws an Exception. Just having...

I'm currently using this `IContainerBuilder` wrapper for this task ```csharp using System; using System.Collections.Generic; using VContainer; namespace App { public class ContainerValidator : IContainerBuilder { private readonly IContainerBuilder _nested; private...

Oof Again, most likely it's not worth it. As you said, it will have performance implications, but more than that it adds some sematics which might be not clear: ```csharp...

Tbh I can see how both `IDisposable` and `CancellationToken` can be used here: - `IDisposable` could cancel new invocations (current implementation) - `CancellationToken` could be linked with the token passed...