Allow serialization of TensorInfo, and other safetensors classes

[LeoDog896]

Feature request

Add missing derive traits for Serialize/Deserialize to TensorView (and other associated types missing these derivations)

Motivation

I am trying to return a safetensors view from its file format into JSON (for WASM bindings), and would like to not need to create a wrapper struct (especially when safetensors already imports Serde and uses its traits on a few select structs)

Your contribution

I can contribute with a PR, but I want this to be confirmed before I add it.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[LeoDog896]

Any opinion on this?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[LeoDog896]

.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[LeoDog896]

.

[Narsil]

Hi @LeoDog896 ,

Sorry for the long wait on this.

I do not understand the need for it. Why do you need to JSON representation of TensorView ?
I'm hesitant to add this, because TensorView doesn't own the data buffer, therefore converting it into JSON (or any serialization) would cause a large copy, which is not immediately obvious when manipulating this struct.

WASM target probably doesn't require JSON intermediary representation of the buffer, does it ?