SWARS is a set of highly opinionated building blocks for building referentially transparent transformations over immutable data.
Provide a standard and coherent way to build referentially transparent transformations over immutable data. Inspired by abstract rewriting systems.
SWID aims to produce binding and projection code that provides end users with rich interoperation. This requires SWID to traverse, analyze and flatten types. In the context of Flutter, these types exist in class hierarchies that are both deep and extremely wide.
For any set of types with common ancestors in the class hierarchy, analysis and code generation performed by SWID will be repeated. In the context of Flutter, this repeat work was seen to consume an extremely long amount of time.
SWARS aims to allow SWID to break up the graph of analyses and code generation tasks for any given type (and any given sub set of any given type) into an arbitrary number of arbitrarily complex operations that can be composed and who's usage sites can be opaquely replaced with their results.
The identities of inputs and outputs in SWARS is uniquely determined by each type that implements
IHashKey. Types are expected to describe how to uniquely identify themselves by overriding
The core concept of SWARS is the term. Terms in SWARS are represented by the
ISwarsTerm interface. Terms can be "called" in order to produce a term result (represented by the
ISwarsTermResult interface). Terms and term results must implement
IHashComparable. SWARS' guarantees about identity and referential transparency are enforced through the implementation of these interfaces. Default implementations are provided by
In cases where terms cannot be uniquely identified based on their inputs (such as when their inputs are closures or types that do not implement the aformentioned interfaces),
SwarsNonUniqueTermMixin can be used to opt a given term out of the identity system.
Transformations and analyses in SWARS are terms with some extra type-level sugar to help express their intended semantics. This is provided by the
ISwarsAnalysis interfaces with default implementations
When SWARS terms are called, an
ISwarsPipeline is always provided. Terms are composed by calling additional terms using the provided pipeline. The exact type of pipeline provided and what that pipeline does with terms that are composed should be completely opaque. A pipeline which caches term results and opaquely replaces term invocations with their results if they've been seen before is provided by
CachingPipeline. The ability to do this safely is guaranteed by the identity and term systems described above.