Fedor Logachev
Fedor Logachev
wow! should we just put this in .cargo and call it a day?
feel free to open a PR! I don't have a musl-based setup to test it out :(
Also I believe for the library it should be done through build.rs, not .cargo. But without a musl environment I can't really test it, so can't really tell how exactly...
Hi! Take a look on the example of using proxy: https://gist.github.com/not-fl3/f40d2025542ef9a4b8c76896343171dc For chrono's datatypes it would be quite similar I believe: you will need to create your own struct with...
Should be fixed in macroquad-tiled 0.2.1!
Sure, sounds like a brand new problem, feel free to open an issue!
Despite the bug, allocating textures and especially render targets each frame would never work really well. Its a really expensive procedure and there are so many things that could go...
If I understand correctly, the tradeoff here: With this PR we disallow using nanoserde with crate rename (like this: `notserde = {package = "nanoserde"}` `use notserde::SerBin;`), but allow using `#[nanoserde::SerBin]`?...
Honestly, I am not convinced `std::` paths make anything better. Especially for types that are actually from `core::`, not `std` And for the `nanoserde::` paths, I just do not have...
I would just use them a is, as `Vec` or `Into`