com-rs VS tch-rs

regarding COM - check https://github.com/microsoft/com-rs

I'm building a crate to show a progress indicator in the icon of the taskbar of the app using it, I already began the implementation for Linux, but I want to support Windows also, for that I need to access ITaskBarList3, I don't knew anything about COM interfaces before find this. The point is that I'm pretty confused about what to do. They said I would implement the functions, but I want to call them, and this thing com-rs, I'm not sure if I would redefine the interface that is already defined in winapi.

I wanted to do something like this but then I would miss on proper CUDA acceleration and lose performance compared to using torchlib.

I wrote a forgettable llama implementation for https://github.com/LaurentMazare/tch-rs (pytorch's torchlib rust binding).

I first encountered OCaml's PyTorch bindings because apparently they generate a C wrapper around PyTorch's C++ API, and Rust's PyTorch bindings use OCaml's C wrapper. See: https://github.com/LaurentMazare/tch-rs

You could try looking at the min-GPT example of tch-rs. I'd also strongly suggest watching Karpathy's video to understand what's going on.

If you pefer to see it in code there's a succint gpt implementation here https://github.com/LaurentMazare/tch-rs/blob/main/examples/m...

Rust is fully compatible w/ C bindings, so even Python libraries written in C can be easily set up to work in Rust (and have been). For example, see PyTorch Rust bindings, which actually works faster than in Python because all of the glue code around the C++ API is in Rust instead of Python.

Pytorch

I have looked into this a bit and found some crates which help in loading torchscript models called tch-rs