danhau

20 ms·

211.
by danhau 5y ago
Isn’t that‘s just an input sanitization problem? If you chuck raw user input into some sensitive piece of code, you‘ve lost - doesn‘t matter whether its passed as a string or not. I don’t see how Rust‘s comptime string formatting is a pitfa
212.
by danhau 5y ago
Very neat, thank you! This could be very handy. Is it open source? I would love to have the ability to display intervals instead of note names (maybe both?).
213.
by danhau 6y ago
I'm not a pro but here are my two cents. The benefit, and really the point of unsafe, is to encapsulate the unsafe stuff behind safe APIs and to use Rust's other features, like the borrow checker for example, to enforce correct us
214.
by danhau 6y ago
The article has a demo link: https://awesomephant.github.io/continuous-typography/
215.
by danhau 6y ago
But that's an apples/oranges comparison, isn't it? C# code in Unity games is predominantly high-level game behaviour / scripting. Most of the heavy lifting is done by Unity behind the scenes. So to me it's even more
216.
by danhau 6y ago
Love the idea. Despite owning a digital amp with all effects I could ever want built-in, it would still be tremendous fun to just try out and experiment with pedals. Could even convince me to buy some.
217.
by danhau 6y ago
Thank you. Couldn't agree more. It seems programmers want errors to handle themselves. It's like they want errors to automagically hook themselves into the entire code base and do "the right thing". Or maybe in other wor