Implementing a static stack usage analysis tool - Embedded in Rust
Implementing a static stack usage analysis tool March 13, 2019 by Jorge Aparicio (This blog covers the implementation details of cargo-call-stack v0.1.2. If you are only interested in using the tool these tweets and the README will give you an idea of what it can do.) Motivation So, why would you ever want to analyze the stack usage of your program at compile time? The obvious answer is when you w
Rust プãƒã‚¸ã‚§ã‚¯ãƒˆã§è‡ªå‹•ã§ Git hook をセットã§ãã‚‹ cargo-husky ã‚’ã¤ãã£ãŸ - ã¯ã‚„ãプãƒã‚°ãƒ©ãƒ ã«ãªã‚ŠãŸã„
npm ã§ã‚ˆã使ã£ã¦ã„ã‚‹ husky ã¨ã„ã†ãƒ„ールãŒã‚ã‚Šã¾ã™ï¼Žã“れ㯠npm install ãªã©ã‚’ hook ã—㦠Git hook を自動ã§ã‚»ãƒƒãƒˆã—ã¦ãれるツールã§ï¼Œãƒªãƒ¢ãƒ¼ãƒˆã«ãƒ—ッシュã™ã‚‹å‰ã®ãƒã‚§ãƒƒã‚¯ã‚’強制ã—ã¦ãã‚Œã¾ã™ï¼Žã‚‚ã¡ã‚ã‚“ CI ã§ã‚‚テストを回ã—ã¦ã„ã‚‹ã®ã§ã™ãŒï¼Œãƒ—ッシュå‰ã«ã‚‚ãƒã‚§ãƒƒã‚¯ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã‚±ã‚¢ãƒ¬ã‚¹ãƒŸã‚¹ã«æ—©ã気付ãã“ã¨ãŒã§ãã¾ã™ï¼Ž Rust ã§ã‚‚ã“ã®ä»•çµ„ã¿ã‚’使ã„ãŸã‹ã£ãŸã®ã§ã™ãŒï¼Œãã†ã„ã†ãƒ„ールãŒç„¡ã‹ã£ãŸï¼†ã¤ãã‚Œãã†ã ã£ãŸã®ã§ cargo-husky ã¨ã„ã†ãƒ„ールをã¤ãã‚Šã¾ã—ãŸï¼Ž github.com 基本的ãªä½¿ã„æ–¹ cargo-husky パッケージを Cargo.toml ã® dev-dependencies ã«è¿½åŠ ã—㦠cargo test を実行ã™ã‚‹ã ã‘ã§ã™ï¼Ž [dev-dependencies] cargo-husky = "1" $ cargo test carg
cargoã®ã©ã“ãŒã„ã„ã®ã‹ | κeenã®Happy Hacκing Blog
κeenã§ã™ã€‚ä¹…ã—ã¶ã‚Šã®ãƒ–ãƒã‚°ã§ã™ã。 LLイベントã«è¡Œã£ã¦ããŸã‚‰ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ã®è©±ãŒã‚ã‚Šã¾ã—ãŸã€‚ ãã®æ‡‡è¦ªä¼šã§cargoã«ã¤ã„ã¦æŒ¯ã‚‰ã‚ŒãŸã‚“ã§ã™ãŒã‚¿ã‚¤ãƒŸãƒ³ã‚°ãŒãªãã¦å–‹ã‚Œãªã‹ã£ãŸã®ã§ãƒ–ãƒã‚°ã«æ›¸ã„ã¦ãŠãã¾ã™ã€‚ ã–ã£ãã‚Šã¾ã¨ã‚る㨠パッケージマãƒãƒ¼ã‚¸ãƒ£/ビルドツールã«è¦æ±‚ã•ã‚Œã‚‹è¦ä»¶ã‚’å’ãªãã“ãªã—ã¦ã„ã‚‹ é¢å€’を見る範囲ãŒåºƒãã€è¦ã¯ãƒ¯ãƒ³ã‚¹ãƒˆãƒƒãƒ—ソリューションã ã‹ã‚‰ä¾¿åˆ© コンパイラã¨åŒã˜æ¯ä½“ãŒé–‹ç™ºã—ã¦ã‚‹ã®ã§ã‚°ãƒ€ã‚°ãƒ€ãŒãªã„ ã˜ã‚ƒãªã„ã‹ãªã¨æ€ã„ã¾ã™ã€‚ã‚ã¨ãƒã‚¤ãƒŠãƒªãªã®ã§ã‚ビã‚ビ動ã。 å› ã¿ã«cargoãŒä¾¿åˆ©ã¨ã„ã†å£°ã®ä¸ã«ã¯crates.ioã§æ¬²ã—ã„パッケージを探ã—ã‚„ã™ã„ã ã¨ã‹ã¿ã‚“ãªå‰²ã¨ã‚»ãƒžãƒ³ãƒ†ã‚£ãƒƒã‚¯ãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã‚’守るã®ã§ç†ä¸å°½ã«ãƒ“ルドãŒã‚³ã‚±ãŸã‚Šã—ãªã„ãªã©ã‚‚ã‚ã‚‹ã¨æ€ã„ã¾ã™ã€‚ 1ã«é–¢ã—ã¦ã¯æœ€è¿‘ã®ã‚ˆãã‚るベストプラクティスを全部やã£ãŸã‚‰ã“ã†ãªã£ãŸã£ã¦æ„Ÿã˜ã§ã™ã。 セマンティックãƒãƒ¼ã‚¸ãƒ§ãƒ‹ãƒ³ã‚°ã§ä¾å˜é–¢ä¿‚を管
Cross-compile and link a static binary on macOS for Linux with cargo and rust
Cross-compile and link a static binary on macOS for Linux with cargo and rust One Go feature which I’m using regularly is cross-compiling Go code to other platforms (usually from macOS to linux-amd64). In Go, this is a built-in feature that “just worksâ€. The following command produces a statically linked ELF binary which can simply be copied and run on a Linux machine: $ GOARCH=amd64 GOOS=linux go
Ensuring Beautiful Commits with rustfmt and Travis-CI | kyle kneitinger
When Style is Standardized, Style Can Be Standard The rust-lang-nursery GitHub organization is a fantastic group of folks building tools for both working in, and working with, the Rust language. One of these tools, rustfmt, is quite helpful for maintaining a consistent code style throughout a project. rustfmt is pretty easy to work with. Its default behavior, when executed on a file, is to check i
1
ランã‚ング
ãŠçŸ¥ã‚‰ã›
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
GitHub - hhatto/cargo-strict: avoid unwrap() method
cargo-make
cargo-fuzz findings
GitHub - rsolomo/cargo-check
GitHub - deadlinks/cargo-deadlinks: Cargo subcommand for checking your documentation for broken links
GitHub - BurntSushi/cargo-benchcmp: A small utility to compare Rust micro-benchmarks.
{{#tags}}- {{label}}
{{/tags}}