johnthagen/min-sized-rust

Feature request: Show effectiveness of each step

Open

#48 opened on Nov 2, 2022

View on GitHub
 (11 comments) (2 reactions) (0 assignees)Rust (4,998 stars) (144 forks)batch import
help wanted

Description

Would be nice to grab a couple random crates and measure average binary size changes for each step and list those as well.

Contributor guide

Tech stack
rust
Domain
performance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with RustUnderstanding of binary size optimization techniques
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
The issue requests a feature to show the effectiveness of each optimization step on binary size. To implement, one should explore the current project structure, likely located in the src/ or examples/ directories, to understand how steps are defined. A potential approach is to write a script that compiles sample crates with each step individually, measure the resulting binary sizes using `cargo size` or `ls l`, and output the deltas. The existing README and any build scripts should be reviewed for guidance. The discussion in comments may provide additional requirements, such as which crates to use for benchmarking.
Feature request: Show effectiveness of each step · johnthagen/min-sized-rust#48 | Good First Issue