> For the complete documentation index, see [llms.txt](https://aisuko.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aisuko.gitbook.io/wiki/freesoftware/programming/rust.md).

# Rust

When I develop rust backend for the [LocalAI](https://github.com/go-skynet/LocalAI) project. Also I have been learning Rust > 2 years in a free time but still 0 experience on it. Most of the time I am focusing on Cloud Native domain with Golang. It is not means I am an expert on Golang, but I am more familiar with Golang than Rust.

So, the founder of [go-skynet](https://github.com/go-skynet) [mudler](https://mudler.pm/) is going to add Rust backend to support more LLM. So, I am going to take this chance to head start my Rust journey. And under the helping of [lu-zero](https://github.com/lu-zero). The framework of the new Rust backend was done. And the next step is to embed ML framework like burn and candle to support more LLM.

So, here I list some of the features of Rust that are helpful for coding in Rust. Here is the link of the mind map

<img src="https://hostux.social/system/media_attachments/files/111/271/860/832/985/099/original/5ee063545ff04e41.png" alt="Xmind for Rust" width="400%">


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://aisuko.gitbook.io/wiki/freesoftware/programming/rust.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
