---

yaml
---
r: 148467
b: refs/heads/try2
c: cb12de1
h: refs/heads/master
i:
  148465: 0e1432e
  148463: 51428fa
v: v3

Author: alexcrichton

[refs]

@@ -5,7 +5,7 @@ refs/heads/snap-stage3: 78a7676898d9f80ab540c6df5d4c9ce35bb50463
 refs/heads/try: 519addf6277dbafccbb4159db4b710c37eaa2ec5
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
-refs/heads/try2: 6f3326f84df3f0781984cf99f2d6b38778ac6c15
+refs/heads/try2: cb12de14c92526930aa9c55e660fe2f7350fb56a
 refs/heads/dist-snap: ba4081a5a8573875fed17545846f6f6902c8ba8d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try2/doc/guide-ffi.md

@@ -249,143 +249,6 @@ fn main() {
 }
 ~~~~
 
-# Callbacks from C code to Rust functions
-
-Some external libraries require the usage of callbacks to report back their
-current state or intermediate data to the caller.
-It is possible to pass functions defined in Rust to an external library.
-The requirement for this is that the callback function is marked as `extern`
-with the correct calling convention to make it callable from C code.
-
-The callback function that can then be sent to through a registration call
-to the C library and afterwards be invoked from there.
-
-A basic example is:
-
-Rust code:
-~~~~ {.xfail-test}
-extern fn callback(a:i32) {
-    println!("I'm called from C with value {0}", a);
-}
-
-#[link(name = "extlib")]
-extern {
-   fn register_callback(cb: extern "C" fn(i32)) -> i32;
-   fn trigger_callback();
-}
-
-fn main() {
-    unsafe {
-        register_callback(callback);
-        trigger_callback(); // Triggers the callback
-    }
-}
-~~~~
-
-C code:
-~~~~ {.xfail-test}
-typedef void (*rust_callback)(int32_t);
-rust_callback cb;
-
-int32_t register_callback(rust_callback callback) {
-    cb = callback;
-    return 1;
-}
-
-void trigger_callback() {
-  cb(7); // Will call callback(7) in Rust
-}
-~~~~
-
-In this example will Rust's `main()` will call `do_callback()` in C,
-which would call back to `callback()` in Rust.
-
-
-## Targetting callbacks to Rust objects
-
-The former example showed how a global function can be called from C-Code.
-However it is often desired that the callback is targetted to a special
-Rust object. This could be the object that represents the wrapper for the
-respective C object. 
-
-This can be achieved by passing an unsafe pointer to the object down to the
-C library. The C library can then include the pointer to the Rust object in
-the notification. This will provide a unsafe possibility to access the 
-referenced Rust object in callback.
-
-Rust code:
-~~~~ {.xfail-test}
-
-struct RustObject {
-    a: i32,
-    // other members
-}
-
-extern fn callback(target: *RustObject, a:i32) {
-    println!("I'm called from C with value {0}", a);
-    (*target).a = a; // Update the value in RustObject with the value received from the callback
-}
-
-#[link(name = "extlib")]
-extern {
-   fn register_callback(target: *RustObject, cb: extern "C" fn(*RustObject, i32)) -> i32;
-   fn trigger_callback();
-}
-
-fn main() {
-    // Create the object that will be referenced in the callback
-    let rust_object = ~RustObject{a: 5, ...};
-     
-    unsafe {
-        // Gets a raw pointer to the object
-        let target_addr:*RustObject = ptr::to_unsafe_ptr(rust_object);
-        register_callback(target_addr, callback);
-        trigger_callback(); // Triggers the callback
-    }
-}
-~~~~
-
-C code:
-~~~~ {.xfail-test}
-typedef void (*rust_callback)(int32_t);
-void* cb_target;
-rust_callback cb;
-
-int32_t register_callback(void* callback_target, rust_callback callback) {
-    cb_target = callback_target;
-    cb = callback;
-    return 1;
-}
-
-void trigger_callback() {
-  cb(cb_target, 7); // Will call callback(&rustObject, 7) in Rust
-}
-~~~~
-
-## Asynchronous callbacks
-
-In the already given examples the callbacks are invoked as a direct reaction
-to a function call to the external C library.
-The control over the current thread switched from Rust to C to Rust for the
-execution of the callback, but in the end the callback is executed on the
-same thread (and Rust task) that lead called the function which triggered
-the callback.
-
-Things get more complicated when the external library spawns it's own threads
-and invokes callbacks from there.
-In these cases access to Rust data structures inside he callbacks is
-especially unsafe and proper synchronization mechanisms must be used.
-Besides classical synchronization mechanisms like mutexes one possibility in
-Rust is to use channels (in `std::comm`) to forward data from the C thread
-that invoked the callback into a Rust task.
-
-If an asychronous callback targets a special object in the Rust address space
-it is also absolutely necessary that no more callbacks are performed by the 
-C library after the respective Rust object get's destroyed. 
-This can be achieved by unregistering the callback it the object's
-destructor and designing the library in a way that guarantees that no
-callback will be performed after unregistration.
-
 # Linking
 
 The `link` attribute on `extern` blocks provides the basic building block for

branches/try2/doc/rust.md

@@ -484,7 +484,6 @@ include:
 
 * `fmt!` : format data into a string
 * `env!` : look up an environment variable's value at compile time
-* `file!`: return the path to the file being compiled
 * `stringify!` : pretty-print the Rust expression given as an argument
 * `include!` : include the Rust expression in the given file
 * `include_str!` : include the contents of the given file as a string

branches/try2/src/libextra/lib.rs

@@ -20,8 +20,7 @@ Rust extras are part of the standard Rust distribution.
 
 */
 
-// NOTE: upgrade to 0.10-pre after the next snapshot
-#[crate_id = "extra#0.9"];
+#[crate_id = "extra#0.10-pre"];
 #[comment = "Rust extras"];
 #[license = "MIT/ASL2"];
 #[crate_type = "rlib"];

branches/try2/src/libgreen/lib.rs

@@ -17,8 +17,7 @@
 //! This can be optionally linked in to rust programs in order to provide M:N
 //! functionality inside of 1:1 programs.
 
-// NOTE: Change to 0.10-pre after snapshot
-#[crate_id = "green#0.9"];
+#[crate_id = "green#0.10-pre"];
 #[license = "MIT/ASL2"];
 #[crate_type = "rlib"];
 #[crate_type = "dylib"];

branches/try2/src/librustc/front/std_inject.rs

@@ -21,8 +21,7 @@ use syntax::fold;
 use syntax::opt_vec;
 use syntax::util::small_vector::SmallVector;
 
-// NOTE: upgrade to 0.10-pre after the next snapshot
-pub static VERSION: &'static str = "0.9";
+pub static VERSION: &'static str = "0.10-pre";
 
 pub fn maybe_inject_libstd_ref(sess: Session, crate: ast::Crate)
                                -> ast::Crate {

branches/try2/src/librustc/metadata/encoder.rs

@@ -1720,7 +1720,6 @@ impl<'a, 'b> Visitor<()> for MacroDefVisitor<'a, 'b> {
             }
             _ => {}
         }
-        visit::walk_item(self, item, ());
     }
 }
 

branches/try2/src/librustc/middle/borrowck/doc.rs

@@ -179,7 +179,7 @@ checker uses a data flow propagation to compute the full set of loans
 in scope at each expression and then uses that set to decide whether
 that expression is legal.  Remember that the scope of loan is defined
 by its lifetime LT.  We sometimes say that a loan which is in-scope at
-a particular point is an "outstanding loan", and the set of
+a particular point is an "outstanding loan", aand the set of
 restrictions included in those loans as the "outstanding
 restrictions".
 

branches/try2/src/librustc/middle/check_const.rs

@@ -177,10 +177,11 @@ pub fn check_expr(v: &mut CheckCrateVisitor,
                 }
             }
           }
+          ExprParen(e) => { check_expr(v, sess, def_map, method_map,
+                                        tcx, e, is_const); }
           ExprVstore(_, ExprVstoreSlice) |
           ExprVec(_, MutImmutable) |
           ExprAddrOf(MutImmutable, _) |
-          ExprParen(..) |
           ExprField(..) |
           ExprIndex(..) |
           ExprTup(..) |

branches/try2/src/librustc/middle/moves.rs

@@ -38,7 +38,7 @@ case, the value is read, and the container (`x`) is also read.
 In the second case, `y`, `x.b` is being assigned which has type
 `~int`.  Because this type moves by default, that will be a move
 reference.  Whenever we move from a compound expression like `x.b` (or
-`x[b]` or `*x` or `{x}[b].c`, etc), this invalidates all containing
+`x[b]` or `*x` or `{x)[b].c`, etc), this invalidates all containing
 expressions since we do not currently permit "incomplete" variables
 where part of them has been moved and part has not.  In this case,
 this means that the reference to `x` is also a move.  We'll see later,
@@ -56,7 +56,7 @@ For each binding in a match or let pattern, we also compute a read
 or move designation.  A move binding means that the value will be
 moved from the value being matched.  As a result, the expression
 being matched (aka, the 'discriminant') is either moved or read
-depending on whether the bindings move the value they bind to out of
+depending on whethe the bindings move the value they bind to out of
 the discriminant.
 
 For examples, consider this match expression: