Replies: 1 comment 1 reply
-
Original reply by @mpvl in cuelang/cue#613 (comment) The core runtime (a bunch of indices) is pretty much safe for concurrency. The adt values are almost safe for concurrency: it is mostly the cycle detection algorithm that is not. The main part that is hard to make concurrent is the API itself, most notably the instance type and its handling. This type is now mostly unnecessary, but it is hard to get rid of it without introducing backwards incompatibility. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Originally opened by @verdverm in cuelang/cue#613
Using Cue in different goroutines is a valid use case that is not supported today.
What would it take to get it there?
Starting this discussion since has been coming up more. Hopefully this can serve as a place to capture the high level design, current impediments, and requirements to get it there.
It may be worthwhile to collect alternative methods (such as exec'n out to cue in the meantime)
Beta Was this translation helpful? Give feedback.
All reactions