The display problem should be resolved simply by passing the info that the data is encoding booleans in burn-jit not impacting the burn_tensor apis

Although less likely to cause issues, this mapping for the bool encoding dtype is also in burn-candle. We should also return U8 for the primitive dtype and not bool in this case.

Since this is specifically for display purposes, perhaps we could fix the Display implementation for tensors? E.g.

writeln!(f, "  shape:  {:?},", self.dims())?;
writeln!(f, "  device:  {:?},", self.device())?;
writeln!(f, "  backend:  {:?},", B::name())?;
writeln!(f, "  kind:  {:?},", K::name())?;

// Bool tensors might be encoded in a different type, which we abstract for the display
let dtype = if TypeId::of::<K::Elem>() == TypeId::of::<bool>() {
    DType::Bool
} else {
    self.primitive.dtype()
};

writeln!(f, "  dtype:  {:?},", dtype.name())?;

Codecov Report

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 82.56%. Comparing base (9c31f75) to head (5d1e443).
Report is 5 commits behind head on main.

@@            Coverage Diff             @@
##             main    #2528      +/-   ##
==========================================
- Coverage   82.59%   82.56%   -0.04%     
==========================================
  Files         827      827              
  Lines      106712   106855     +143     
==========================================
+ Hits        88143    88226      +83     
- Misses      18569    18629      +60     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests