google/comprehensive-rust

Expand the "Why Rust?" section

Open

#132 opened on Jan 9, 2023

View on GitHub
 (0 comments) (2 reactions) (0 assignees)Rust (2,009 forks)batch import
good first issue

Repository metrics

Stars
 (32,954 stars)
PR merge metrics
 (Avg merge 9d 23h) (36 merged PRs in 30d)

Description

Actually I think we need more explanation about why we need and when to use. Rust is built with years of experience in software engineering but not every learner knows where these smart designs of Rust come from...

Originally posted by @Luosuu in https://github.com/google/comprehensive-rust/discussions/32#discussioncomment-4615986

Contributor guide

Research direction
Explain the historical context of Rust's design, referencing existing course material and external resources like the Rust Book and related discussions.
Tech stack
rust
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Basic knowledge of Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70