Params in Jobs

I assume there's no safe way to use the 'params' keyword from inside a Job. Calling out to a method that takes a params array would...allocate an array, and therefore wouldn't be blittable.

Still, the params syntax is mighty useful. And the size of the array could be known at compile time. So I was wondering if anyone has found a way around this.

I don't believe there's any way to use a custom collection type with the params keyword (MS Docs seem to suggest it's hardcoded to only every use an array). But maybe I'm mistaken?

 

Why don't you use a NativeArray of whatever you want to pass in? Sure the syntax might be slightly less appealing, but from my understanding, params has always been horrible for performance due to the garbage generation anyway.

 

That's really the only reason someone might want to.

I haven't used them in general (using Native Collections instead), because at the end of the day, perf usually comes first.

Just wondering if anyone's come up with a good way that doesn't also sacrifice performance.