Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/hdescobarh/rustaceology-logbook
My journey learning Rust
https://github.com/hdescobarh/rustaceology-logbook
exercises rust
Last synced: 27 days ago
JSON representation
My journey learning Rust
- Host: GitHub
- URL: https://github.com/hdescobarh/rustaceology-logbook
- Owner: hdescobarh
- License: mit
- Created: 2022-05-06T06:00:20.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-11-24T00:58:28.000Z (about 1 year ago)
- Last Synced: 2024-10-20T15:46:08.438Z (3 months ago)
- Topics: exercises, rust
- Language: Rust
- Homepage:
- Size: 624 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Rustaceology Logbook 🦀
![Rust](https://img.shields.io/badge/-Rust-B7410E?logo=rust&logoColor=28282B&labelColor=white)
![VSCode](https://img.shields.io/badge/-VSCode-blue?logo=visualstudiocode&logoColor=blue&labelColor=white)
![License](https://img.shields.io/github/license/hdescobarh/rustaceology-logbook)I am interested in using computing to address biological questions. Although I was familiar with interpreted languages like Python and Java, I wondered if I should learn a compiled language. I was reluctant because languages like C++ have complex syntax; besides, I did not find an immediate practical usage for a compiled language in the scientific context.
However, after I read *["Why scientists are turning to Rust"](https://doi.org/10.1038/d41586-020-03382-2)* in *Nature*, I got the motivation to start the journey of learning Rust. This repository is to follow my progress and to keep me motivated 💪🏽.
The repository has the following folder organization:
## 📙 Notes
1. It contains multiple subfolders with Rust projects; most of them are adaptations of the bibliography's examples. I intend to make the source code self-explanatory and preserve annotations at a minimum. Since I do not want to spend time deciding on a good subfolder organization, I will broadly follow the same numeration as in *The Rust Programming Language* book.
2. There is an autogenerated Markdown file containing the source code of all projects. Having all notes in a single place makes me more comfortable when reviewing them.
3. There is a folder for manual notes about relevant topic to understand how Rust works.
## 🏃🏽 Exercises
Subfolders contain projects I made as exercises; there are no strict rules for naming them.
## 📚 Bibliography
It stores the bibliography in a single BibTeX formatted file.