Skip to content
New issue

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

Share By Communicating #120

Closed
azul3d-bot opened this issue Mar 6, 2016 · 1 comment
Closed

Share By Communicating #120

azul3d-bot opened this issue Mar 6, 2016 · 1 comment

Comments

@azul3d-bot
Copy link

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:

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.

@azul3d-bot
Copy link
Author

Fixed/merged as part of #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant