> base64.rs: > let s = [52, 53, 54].to_base64(STANDARD); > > => why adding the "standard" argument? One will ALWAYS want the "STANDARD" method of creating the base64 representation of some bytes, why not adding this argument as default.
That is not true. If you are going to be putting the Base64 encoded data into a URL you're going to have to use URL_SAFE instead of STANDARD. If you're trying to send an email, you'll need to use MIME instead of STANDARD. If you're talking to a service that requires one of the ~10 other variants of Base64, you'll need to use a custom config struct. Steven Fackler On Mon, Nov 11, 2013 at 5:23 PM, Brendan Zabarauskas <[email protected]>wrote: > On 12 Nov 2013, at 10:12 am, John Clements <[email protected]> > wrote: > > > If you had the energy to build an alternate front-end using a > parenthesized syntax, I'm sure there are others that would give it a try. > Me, for instance! > > It would be nice if we could: > > - A: desugar Rust into a small kernel language > - B: allow rustc to take in some sort of raw AST data (not sure if that’s > already possible) > - C: have a way of outputting the AST data in a certain syntax. > > That would allow folks like me to have a nice Haskelly syntax as well as > an s-expr style! > > Heh. > > ~Brendan > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
