Plugin feeding some invalid data to debugger in Visual Studio Code

[DeanRoddey]

I wasn't sure whose issue this was so I started on the VSC repo. I'm having some problems with some values being displayed correct when debugging Rust in VSC. They said that this had to be the Rust plugin, which is responsible for providing the already formatted values to the debugging interface. Here's a link to the original issue over there. One of the Rust guys there responded and said you could ping him if you had questions:

microsoft/vscode#95580

You can see here a local character being created, and what shows up for in the debugging pane. All characters show up this way. The actual character value doesn't matter, it always shows an error instead of the value.

There's also apparently some issue with displaying string slices which may be related. The original string will be OK, then a slice gets passed to a method, and inside there it's completely whacked, showing a huge slice size and garbage in the values. I can get a screen cap of that if you need.

[rhymu8354]

I'm new to Rust, trying to debug Rust code in VSCode, and seeing the issue with slices. Here's a very simple example reproducing the problem:

fn first<T>(v: &[T]) -> Option<T>
    where T: Copy
{
    if v.is_empty() {
        return None;
    } else {
        return Some(v[0]);
    }
}

fn main() {
    let data = vec![3, 5];
    println!("First of {:?} is {}", data, first(&data).unwrap());
}

Changing the code to work with a &Vec<T> rather than a &[T] works around the debugger issue:

[DeanRoddey]

So at least it's not just me... That's exactly what I see as well. I should have provided a screen cap for that one as well.