Lokathor
Lokathor
I would absolutely love if the `proc_macro` crate provided the info about the target to the proc-macro in a structured, programatic way, rather than checking environment variables.
We could just write them directly in assembly. I did that recently, it wasn't bad at all.
So to be extra clear, if we remove the comments but don't change the code at all that would be sufficient to use the standard MIT/Apache of other rust crates?
People can also file a PR of course.
I license past and future contributions under the triple MIT OR Apache-2.0 OR Zlib license, allowing licensees to choose any one at their option.
We also need an entry for `armv7-unknown-linux-gnueabihf`, the raspberry pi family. We also might as well add other targets with a stdlib. There's no actual blocker for this change but...
0.2 is a pretty old version of beryllium at this point. It's entirely possible that the crate just wasn't doing a static build back then, I don't even remember. Did...
That's quite the wild linker error. I'm not eve slightly sure how you'd fix it. If using the DLL fixes things then you should do that.
I suppose. I'm not familiar with those but if they're basically normalish simd types that sounds fine.
I'm just double checking recent open issues, and that does seem correct at a glance. You don't even need the Copy bound. Any type at all wrapped with MaybeUninit can...