Bug: range access of 3-d Tensor.

[0h-n0]

Hi, thank you for developing a wonderful crate.
I found a bug in range access to 3 dimension tensor. The following code is minimal reproduce code. When I access the tensor with index, i can get a correct answer. However, when I access the tensor with range, the first item is completely wrong.

extern crate tch;                                                                                                                          
                                                                                                                                           
use tch::IndexOp;                                                                                                                          
                                                                                                                                           
fn main() {                                                                                                                                
    let x: Vec<i64> = (0..24).collect();                                                                                                   
    println!("{:?}", &x);                                                                                                                  
    let x = tch::Tensor::of_slice(&x).view((2, 3, 4));                                                                                     
    println!("{:?}", x.i((0, 0, 0)));                                                                                                      
    println!("{:?}", x.i((0..2, 0, 0)));                                                                                                   
}   

the result is here,

[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23]                                                     
[0]                                                                                                                                        
[93848231074208, 16] 

[LaurentMazare]

Thanks for reporting this, I just pushed a fix that should hopefully solve this issue.
Interestingly this was caused by a dangling pointer in the C++ layer which is a good argument for using rust rather than C++ as the borrow checker would easily have spotted the problem (commit link in case you're curious).