requirement]. I'm hoping to use Go but I can't figure out if libfuse
callbacks are safe within go: there will be a bunch of C threads calling
into go. From what I can tell this definitely used to be unsafe
but since late 2012 it appears to possibly be supported. Issue 4435 seems
like it might've been the relevant fix
I've ported the hello world example to go
[http://fuse.sourceforge.net/helloworld.html] with cgo using the gateway
functions required. Definitely seems to work. But I don't have a clear
sense of whether or not I'm likely to destroy the heap or what happens when
more highly concurrent calls come in. Is it working because it's read-only?
Is it actually safe to do this? This thread and the resolution to 4435
suggest that having non-go threads call in [if done correctly] is okay.
Can anyone provide a bit of updated guidance?
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.