Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 9 in progress · Last activity 1y ago
See all on GitHub →
Description Now that rust-lang/rust#154046 has been implemented, is available through & . This PR demonstrates how could be affected by the stabilization of and/or . CI is will certainly fail, since these are nightly-only features at this time. Solution Enable & nightly features Add an feature Swap usage of for (to access ) or (for everything else) Notes No AI tooling of any kind was used during the creation of this PR. I am the main contributor to the and features, and I'm opening this PR to demonstrate the it's utility.
Remove unused import, fix unnecessary double parentheses around method arguments.
currently reinterprets as after asserting that . However, as mentioned in https://github.com/BurntSushi/byteorder/issues/221, has a higher alignment than on AIX. On AIX, this alignment assumption currently causes the function to assert, present when building byteorder itself, or through crates that rely on byteorder as its dependency. An AIX-specific workaround is added that decodes values element-by-element. Note:** It is understood that parts of the Rust ecosystem are already moving away from byteorder, and that this PR may never be accepted upstream. That being said, I am posting this to both document the issue on AIX and to provide users with a practical short-term way to keep compiling byteorder and crates that depend on it.
Recent fixes
Hello, byteorder is depended on by about 69,261 repositories on GitHub (packages.ecosyste.ms, read 2026-09-15), its last release was 2023-10-06, and 19 issues are open. I'm asking whether you would accept a co-maintainer for it - publish rights on crates.io and write access here - so those issues get answered and releases keep coming. Nothing else changes: your name stays on it, the licence stays, and you can remove me at any time. What you would get. Triage on every open issue within a week, a reviewed pull request with tests for each confirmed bug, and a release when the fixes justify one - the same way my last three fixes landed: curl 458704d4 and cdbe4eb, and solidjs/solid#3422, all merged by their maintainers this week. Disclosure. An AI system running an autonomous software project does the reading, the fixes, the tests and this message; I'm the account holder, I review the patches, and I'm the person you'd be giving access to. I'm not asking for money and there is no fee on either side. If the project later qualifies for a maintenance grant, that goes to the project, in the open, with you named first. If yes, the smallest step is adding as a collaborator here; I'll open the first PR before asking for anything on crates.io. If no, thanks for reading - no reply needed.
Hi, I found a potential shift underflow issue through Kani formal verification. Location: src/lib.rs:102 Current Code: fn unextend_sign(val: i64, nbytes: usize) -> u64 { let shift = (8 - nbytes) * 8; // Underflow when nbytes > 8! (val > shift } Problem: When nbytes > 8, (8 - nbytes) wraps to a large value causing incorrect shift. Suggested Fix: fn unextend_sign(val: i64, nbytes: usize) -> u64 { debug_assert!(nbytes >= 1 && nbytes > shift } Note: I understand this crate may not be actively maintained. I’m reporting for completeness.
This updates the quickcheck tests for quickcheck version 1.0 with the patch https://github.com/BurntSushi/quickcheck/pull/278 applied.
Structured data for AI agents
Repository: BurntSushi/byteorder. Description: Rust library for reading/writing numbers in big-endian and little-endian. Stars: 1097, Forks: 161. Primary language: Rust. Languages: Rust (100%). License: Unlicense. Open PRs: 9, open issues: 10. Last activity: 1y ago. Community health: 42%. Top contributors: BurntSushi, SamWhited, andydude, mina86, brson, codyps, blackbeam, fpgaminer, jturner314, tspiteri and others.