Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updated q/a on constructors - closes #2 and #3 #4

Merged
merged 1 commit into from
Apr 16, 2024
Merged

Updated q/a on constructors - closes #2 and #3 #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,11 +50,14 @@ The full API documentation can be found [here](wasi-proposal-template.md).

Although `embedded_hal` takes this approach, I would keep them separated for now. At least until each proposal is at least in Phase 2.

#### Why are there no constructors for the i2c interface? How does one obtain an i2c handle?

I2c resources will be constructed in many different ways on different devices, so worlds that include the i2c interface should also include a way to obtain i2c handles. Typically this will either be by having i2c handles passed into exported functions as parameters, or by having i2c handles returned from imported functions.

### Stakeholder Interest & Feedback

TODO before entering Phase 3.


### References & acknowledgements

Many thanks for valuable feedback and advice from:
Expand Down