We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue by slimsag Sunday Dec 14, 2014 at 08:54 GMT Originally opened as azul3d-legacy/gfx#66
Right now the gfx package makes extensive use of mutexes. It is commonplace today to write code like:
gfx
object.Lock() object.Textures[0].Lock() object.Textures[0].Source = foo object.Textures[0].Unlock() object.Unlock()
This is not efficient or okay in any way.
The text was updated successfully, but these errors were encountered:
Fixed/merged as part of #1
Sorry, something went wrong.
No branches or pull requests
Sunday Dec 14, 2014 at 08:54 GMT
Originally opened as azul3d-legacy/gfx#66
Right now the
gfx
package makes extensive use of mutexes. It is commonplace today to write code like:This is not efficient or okay in any way.
The text was updated successfully, but these errors were encountered: