praeclarum

using System;
using System.Threading;
using System.Threading.Tasks;
using System.Collections.Concurrent;

namespace Praeclarum
{
	/// <summary>
	/// Wraps a value and only allows access to it using a single thread
	/// of execution (see SingleThreadQueue).

non

Introduction

Machinist Issue #2 asks:

Is it correct, that this stuff is completely obsolete now due to value classes or are there still some use cases? An example of using value class for zero-cost implicit enrichment: [...]

The short answer is that Machinist is not obsolete: value classes existed before the Machinist macros were implemented, and they do not solve the

gigamonkey

Write a program that does what it’s supposed to do
Write idiomatic code
Debug a program that you wrote
Debug a program someone else wrote
Debug the interaction between a system you wrote and one you didn’t
File a good bug report
Modify a program you didn’t write
Test a program you wrote
Test a program you didn’t write
Learn a new programming language