> For the complete documentation index, see [llms.txt](https://docs.bdurham.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdurham.dev/old-projects/rust-basics.md).

# Rust Basics

{% embed url="<https://github.com/thebriandurham/Rust-Basics>" %}

## About

* Followed guided learning experience to get a better grasp of the Rust programming language so that I can make more performant offsec tools that can easily be compiled for various operating systems.
* Learned the foundations of Rust, including: using Cargo, data-types, error-handling, functions, control flows, etc.
* Created a single threaded web server to learn the basics of networking, sockets, and requests in the rust language.

## Postmortem

Ah, Rust. How do I love thee? Let me count the ways. But seriously, I do love Rust and this was a great intro to it. One day, when I'm not so busy, I'll actually go back and rewrite all of my old code in Rust. But, and I gotta say it, for now Python is my mainline for quickly whipping up tooling during engagements and for personal side projects.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bdurham.dev/old-projects/rust-basics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
