3 ms·
You'd just need to have a mutex lock on the values. That could be slow, but you probably don't want to have a config flag in a hot loop anyways. :) In Nim you
by elcritch 4y ago
You'd just need to have a mutex lock on the values. That could be slow, but you probably don't want to have a config flag in a hot loop anyways. :)
In Nim you can do compile flags which let you set constants so you avoid the problem:
const myLibraryVersion {.intdefine.} = 3
- masklinn 4y ago> You'd just need to have a mutex lock on the values. Oh no they're saying that it's thread-safe, that's not an issue. Rather that depending on the order of initialisation, possibly of different systems entirely, you can have different initial states because different systems or subsystem decided of the default value.