neuronika VS winsafe

Check where and how this struct is used. https://github.com/neuronika/neuronika/blob/variable-rework/neuronika-variable/src/history.rs

Also you can take a look at neuronika.

There is also https://github.com/neuronika/neuronika

I have a question: as the maintainer of [neuronika](https://github.com/neuronika/neuronika), a crate that offers dynamic neural network and auto-differentiation with dynamic graphs, I'm looking at a future possible feature for such framework consisting in the possibility of compiling models, getting thus rid of the "dynamic" part, which is not always needed. This would speed the inference and training times quite a bit.

If you like autograd you will love neuronika

After reading most of the book, I wanted to get my hands dirty. My initial idea was to build a small machine learning framework but I deemed it to be too difficult if not impossible for me at the time. (Now, neuronika would have something to say). When gathering the bibliography for my thesis, I recalled to have stumbled upon a particular algorithm, t-SNE, whom I liked very much. I found the idea behind it to be very clever and elegant (t-SNE it's still one of my favorite algorithms, together with backprop and SOM, I find manifold learning fascinating in general). "So be it", I said, and I began writing a mess of a code, that was basically a translation of the C++ implementation. Boy was it bad.

me and a colleague of mine are developing neuronika

Nobody has the audacity to really push forward this statement, at least not in scientific computing, that I know of. Personally, the lack of somewhat stable GPU computing and some key features of Rust, which are still unstable are slowing the development of neuronika.

You're lucky, I also wrote one.

I've done a migration from C++ to Rust having experience with both, and it was not easy.

Let me know if these suit you. Feel free to open an issue if you need anything.

Maybe you'd like this.

Recently I ran into this exact problem when migrating some methods into traits in WinSafe. I used to return impl Trait when the methods belonged to a struct, but now belonging to a trait the compiler yelled at me.

An idiomatic Rust API would add a layer on top of that, providing safe abstractions and taking advantage of lifetime guarantees, which is what the winsafe crate aims for. Of course, you can't automate this kind of thing, so it's very laborious, and it probably will never cover 100% of the vast Win32 API surface.

I write C++ and raw Win32 for more than 20 years. I'm the author of this, and I'm rewriting my personal stuff in Rust just for fun.

Source: I'm the author of a safe Windows API port for Rust, including the API + a full-featured UI layer. I believe I have a fairly elegant model now (zero macros on the user side!), but it took me months of research and many sleepless nights until I could put all the pieces together.

I know what I'm talking about because I authored this, and boy it gave me a hard time.