emberian
emberian
The tool should be separate from cargo, with a subcommand that shells out to it.
It may also be wise to use some sort of interning for things like tags or commands. Servo uses the excellent [string_cache](https://github.com/servo/string-cache) library.
Source also gets cloned; where should that go? On Fri, Mar 7, 2014 at 12:08 AM, o11c [email protected] wrote: > ~/.local/lib/rust would be more standard > > — > Reply...
@lamarqua any update on this?
@neuschaefer I think there is zero risk of it being interpreted in that way. Thanks though!
supercop also has facilities for measuring timing variations, which would be a good _start_ for showing rust-crypto's worthiness.
I'm very interested in working on this, for using ct-verif with some vectorized Rust cipher implementations. However, I'll definitely need some pointers on where this sort of change would need...
@untitaker one needs to reproduce that copyright header from each project that one includes code from, the issue isn't the copyright notice from a single project. It's not unreasonable for...
@untitaker Google's lawyers seem to think so, yes. See also [this](https://www.quora.com/Does-the-MIT-license-require-attribution-in-a-binary-only-distribution), which agree with this interpretation.
@untitaker it's a potential usecase, I'm not proposing it be added to the standard distribution at this time (although I do love iron and handlebars!)