rust-embedded / rust-embedded/rust-sysfs-gpio

non async io in async code

Open
#75 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
397
Forks
48
PR merge metrics
No merged PRs in 30d

Description

I want to ask why you have non sync operation from fs like write_all read_to_string
Looks like you need use tokio::fs

Or if it is ok, can you please tell why it is so

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the async code paths that use fs::write_all and fs::read_to_string, and compare them with the tokio::fs alternative mentioned in the issue. Determine whether the current operations can block; done means the reason for the chosen I/O approach is established and any required change is covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
embedded-iot, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.