Well, reading up more on the Unity Burst compiler and it looks like this is exactly what they're doing. Non-GC subset of C#.. So structs only, data stored mostly within the "Job" and on the stack (and presumably some "engine data" you can access safely (but not own or delete)?)https://twitter.com/ssylvan/status/976233614349225984 …
-
-
I think it could work if all of the "data organization" stuff happens outside of the scripting code. So the "job" sees some input/output data buffers and can have some "owned" data structures embedded in the job. Everything else happens outside of the job.
-
I’m not convinced GC is an issue for that kind of code even in a full-GC language. This is what a good generational GC will excel at… It’ll be an interesting experiment.
- 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.