Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Tonight I'll publish an 0.0.2 which marks that as unsafe and adds the appropriate unsafe {} blocks to the generated code. I was hoping that this would cause that generated code to be flagged by #![warn(unsafe)], but it looks like the linter ignores warnings originating in code generated by external crates, so even #![forbid]ding it has no effect.
I didn't expect people to be looking so closely at this. :P Added the license files and author metadata
Perhaps submit unbounded to the rustsec advisory-db?
I disagree. Rust is statically typed but we build good enough libraries to make working with matrices easy enough, the data scientists will rarely have to type them out themselves as they can be inferred. I was working with glam just recently and it's a very nice matrix library in which I didn't have to mess with the type system at all. There is also REPL to support rust https://github.com/google/evcxr that could be improved.