## High Concept ## This small library is for getting results from a job back onto the main thread or into other jobs. It can do this in one of two ways: - Using a single allocated `Result` that is conceptually a wrapper around a `NativeArray` with a length of 1. - Using a smart `Result` that allows multiple jobs to collectively create a result in parallel. For example, a `Result` would allow an IJobParallelFor to add up a bunch of numbers in parallel. ## `Result` ## The `NativeArray` with a length of 1 has been the goto method for getting computed results from a job back onto the main thread. While completely workable and performant, it leaves a little to be desired when it comes to code clarity. Using `Result` instead of a `NativeArray` of length 1 ensures that nobody (including you!) will ever go and mess with the length of that array accidentally because they didn't know it was an array for storing results. The type of the data structure enforces the amount of data it holds. ## `Result` ## While `Result` is a simple convinience, `Result` is the real magic sauce. Currently if you want multiple threads to contribute to a single result, there are not exactly any built in ways to do that. If you want to sum up multiple values accross different threads, there isn't really a built-in way that can be accomplished. `Result` is a generic data structure that allows multiple threads to contribute to a _single_ result in parallel. For example, `Result` is a container that represents a single integer result. This container supports the Sum operation, and allows jobs to add values to the result from multiple threads at the same time. For example, here is a simple job to add up all the values in an array in parallel: public struct AddValues : IJobParallelFor { [ReadOnly] public NativeArray values; public Result.Concurrent sum; public void Execute(int i) { sum.Write(values[i]); } } public void Update() { var sum = new Result(Allocator.Temp); new AddValues() { values = values, sum = sum }.Schedule(values.Length, 32).Complete(); Debug.Log("The sum is " + sum.Value); sum.Dispose(); } Part of the magic of `Result` is that it doesn't just allow taking the sum of integers, it supports floats as well! In fact, it supports doubles, Vector2, Vector3, and all the rest of the things you might want to sum. And is easily extensible if you wanted to sum things not currently implemented here. And in addition, `Result` doesn't just support adding things up, it supports lots of different operations. For example, here is how you find the maximum value of an array of doubles in parallel: public struct FindMaximum : IJobParallelFor { [ReadOnly] public NativeArray values; public Result.Concurrent max; public void Execute(int i) { max.Write(values[i]); } } Technically, it supports any operation that is Commutative (order doesn't matter), and has an Identity element. For example, addition is supported because addition is comutative, and addition has an identity element of 0. ## Examples ## ![](https://camo.githubusercontent.com/72b8bae02a9a9f31cae39352f9e49ba1138afedf/68747470733a2f2f692e696d6775722e636f6d2f42626c777547342e676966) This is an example of using a `Result` to add up all of the colors in a texture to calculate the average. The quad on the left is procedurally generated in one job, and then a second job calculates in parallel the average color to be displayed on the right quad. ![](https://camo.githubusercontent.com/cc5f19a0169c9d1e41371f2b60eddce4e42e1d94/68747470733a2f2f692e696d6775722e636f6d2f716e4535415a772e676966) This is an example of using a `Result` to calculate the maximum bounds of a large number of particles. The particles are simulated procedurally in one job, and then a second job calculates the bounding box of all of the particles in parallel.