Remove example code dependencies about voodoo HOT 8 CLOSED

You're right. I'll clean those up tomorrow or the next day.

from voodoo.

f31290f

Thanks for catching this :)

from voodoo.

Hey, you mind updating this on crates.io? :D

from voodoo.

No problem :)

Since you're here, I hope you don't mind if I pick your brain for some opinions...

What else do you think we can do make this library better? What do you think of renaming builders as mentioned in #1? Are there any other ergonomic improvements you can think of?

from voodoo.

Using it here. There are a couple of small things I'll try and make PRs for later when I get some time. Overall have enjoyed the API so far. Don't have much to comment on structs versus builders--the builders seem to make sense given that you deviate from the original C structs in minor ways, and allow for default values. I haven't used e.g. ash so I don't know what the alternative feels like in Rust.

from voodoo.

Please don't hesitate to put forward any ideas (PRs or otherwise) you might have about how the API can be improved. Random ideas welcome. This library is an experiment in finding a balance between minimalism/performance/control and ergonomics/usability/ease-of-use.

I've been reluctant to spend too much time documenting until I get more feedback but documentation is probably the area in most urgent need of work. Please continue to point out any rough or confusing things you run into. I can't promise I'll have time to make the documentation perfect any time soon but I'd like to at least have a good list of problems and trouble spots so that the low hanging fruit can be addressed first.

from voodoo.

No worries. The documentation doesn't bother me since it's very close to the spec. The only potential hangups are where it differs/the abstraction is unclear.

from voodoo.

Yes, please point out those areas when you run up against them if you would. I definitely have a blind spot for what is or isn't clear.

from voodoo.