busterwood / goodies

Useful stuff missing from .NET for example duck typing, CSP channels, caching, money, typed ids...

BusterWood.Goodies

So much useful & free stuff for .NET, built as a library for .NET Standard 2.0.

Selected highlights

• BusterWood.Batching namespace contains classes for batching together asynchronous method calls for efficiency.
• BusterWood.Caching namespace contains time and space effecient Cache<,> and ReadThroughCache<,>.
• BusterWood.Channels namespace contains CSP-like communication between (logical) asynchronous threads, including buffered and multicast channels.
• BusterWood.Collections namespace contains the time and space effecient UniqueList<> which implements both IList<> and ISet<>. Additionally HashLookup<,> and CircularQueue<> classes are provided.
• BusterWood.Ducks namespace contains run-time duck typing.
• BusterWood.Equality namespace contains run-time creation of equality comparers using property names.
• BusterWood.Goodies namespace contains structs to ensure you don't mix up your customer and order identifiers, and extension methods for arrays, enums, TimeSpans and strings.
• BusterWood.Linq namespace contains 20% faster LINQ via batching, additional LINQ methods and asynchronous enumerables.
• BusterWood.Logging namespace contains Log static class for structured logging to Console.Error (StdErr).
• BusterWood.Mapping namespace contains extension methods for copying objects with rules for name and type conversion.
• BusterWood.Monies namespace contains Money struct to ensure that you don't add accidentally add GBP and USD together.
• BusterWood.Reflect.Emit namespace contains extension methods for emiting IL via ILGenerator.
• BusterWood.Restarting namespace contains RestartMonitoring that monitor failures in asychrous processes and restarts them on failure (with delay).
• BusterWood.Testing namespace contains a simple testing library inspired by Go's testing package

goodies's Issues

Unexpected behavior and Misleading comment in Select.ExecuteAsync

So here is function.
From comments I expect to get true after one of select statement get executed.
But instead in that case code returns false.
Even without any comment I expect to get true if everything went fine.

So code should
return !timedOut;
instead of return timedOut;
also
for infinitive timer we always should return true not false
if (timeout == System.Threading.Timeout.InfiniteTimeSpan || timeout == TimeSpan.MaxValue)
{
await ExecuteAsync();
return true;//!!!!!!!!!!!!!!!!!!!
}

  /// <summary>Tries to reads from one (and only one) of the added channels.  Does no action if the <paramref name="timeout"/> has been reached</summary>
        /// <returns>True if an action was performed, False if no action was performed and the timeout was reached</returns>
        public async Task<bool> ExecuteAsync(TimeSpan timeout)
        {
            if (timeout == System.Threading.Timeout.InfiniteTimeSpan || timeout == TimeSpan.MaxValue)
            {
                await ExecuteAsync();
                return false;
            }

            var timedOut = false;
            var receiveTimeout = new ReceiveCase<DateTime>(Timeout.After(timeout), _ => timedOut = true);
            var idx = cases.Count;
            cases.Add(receiveTimeout);
            await ExecuteAsync();
            cases.RemoveAt(idx);
            return timedOut;
        }

Memorise DbReader

If a DbRead r could be decorated with memorisation then it could be enumerated multiple times

AsyncEnumerable extensions

Where, Select and other asynchronous methods should be defined on AsyncEnumerable, not AsyncEnumerator

Batching and read-through caching

...are closely related, but don't share any code in this repository

Relationalships

Each().HasMany()
Each().HasOne()