Boscop
Boscop
Btw, in the meantime, there is a macro for this: https://crates.io/crates/closure It supports `clone` (e.g. `closure!(clone first, clone mut second, || { .. })`, `move` (e.g. `closure!(move first, move mut...
@estebank I agree, we should build upon existing syntax. @burdges But why use an equal sign there? Wouldn't this be the most natural syntax? ```rust impl Point { fn x_mut(Point...
Btw, was it already decided if we only want to allow partial borrowing for the methods/self or in general for all arguments (e.g. args of free functions or non-self args...
I agree, I found myself wishing for the ability to give getters a different name that makes more sense to the outside. I think the syntax could be `#[getset(get =...
(A similar issue occurs when I have `#[getset(get = "pub", get_mut = "pub")]` on a field, but forget to derive `MutGetters` (when I only have `Getters`), then there is also...
@Hoverbear Yes, it would be nice to have this, too. Both of these usability improvements are orthogonal (#49 is about the field attributes, this is about the struct attributes), so...
Chrome at least.
It's not that important, I can wait :) (#27 is my main issue atm.)
Btw, Rust is getting nested group imports: https://github.com/rust-lang/rfcs/pull/2128
Basically, crates are compilation units (either lib or bin) and when you do `extern crate foo;` it also imports `foo` into the current scope, so you can use symbols from...