Loom is a testing tool for concurrent Rust code. It runs a test many times, permuting the possible concurrent executions of that test under the C11 memory model. It uses state reduction techniques to avoid combinatorial explosion.

CURLM_OUT_OF_MEMORY (3)

You are doomed.

In programming languages, monomorphization is a compile-time process where polymorphic functions are replaced by many monomorphic functions for each unique instantiation.[1] This transformation is desirable, since then the output intermediate representation (IR) will have concrete types and can be optimized better. Furthermore, most IRs are designed to be low-level and do not support polymorphism. Code generated this way is typically faster than boxed types, but may compile slower and take more space due to duplicating the function body.[2][3][4][5][6][7]

promoted by American software engineer and instructor Robert C. Martin,[1][2][3] first introduced in his 2000 paper Design Principles and Design Patterns.[2][4]

The SOLID ideas are

The single-responsibility principle: "There should never be more than one reason for a class to change."[5] In other words, every class should have only one responsibility.[6] The open–closed principle: "Software entities ... should be open for extension, but closed for modification."[7] The Liskov substitution principle: "Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it."[8] See also design by contract.[8] The interface segregation principle: "Many client-specific interfaces are better than one general-purpose interface."[9][4] The dependency inversion principle: "Depend upon abstractions, [not] concretions."[10][4]