767: allow #[init] and #[idle] to be externed r=korken89 a=wiktorwieclaw
I updated `rtic-macros` to a allow init and idle to be externally defined.
## Design notes
* Updated `extern_binds` example to include external #[init] and #[idle] functions.
* Added docs to Local and Shared structs. The `extern_binds` example has a `#![deny(missing_docs)]` which caused some issues.
## Testing
Apart from building the example, I also used this feature in one of my projects and ran it on a MCU [here](98ca7bd42e/crates/cansat-stm32f4/src/main.rs (L59-L74))
## Related issues
* https://github.com/rtic-rs/rtic/issues/505
## Related PRs
* https://github.com/rtic-rs/rtic-syntax/pull/71
Co-authored-by: Vixu <lonevixu@gmail.com>
759: ci/releasetuning r=korken89 a=AfoHT
- CI: Cargo doc for both pre and post v2
- CI: Make it clearer why a branch push was omitted
- ci: Use job outputs
Co-authored-by: Henrik Tjäder <henrik@tjaders.com>
754: Update pretty_env_logger requirement from 0.4.0 to 0.5.0 r=korken89 a=dependabot[bot]
Updates the requirements on [pretty_env_logger](https://github.com/seanmonstar/pretty-env-logger) to permit the latest version.
<details>
<summary>Commits</summary>
<ul>
<li><a href="0e238400e1"><code>0e23840</code></a> v0.5.0</li>
<li><a href="4dde161d21"><code>4dde161</code></a> deps: env_logger 0.10</li>
<li><a href="f9e35b6dbb"><code>f9e35b6</code></a> Update env logger (<a href="https://redirect.github.com/seanmonstar/pretty-env-logger/issues/49">#49</a>)</li>
<li><a href="93d6d19e06"><code>93d6d19</code></a> Run CI on linux,mac,windows using GitHub actions (<a href="https://redirect.github.com/seanmonstar/pretty-env-logger/issues/51">#51</a>)</li>
<li><a href="5cb49cade2"><code>5cb49ca</code></a> Update README.md (<a href="https://redirect.github.com/seanmonstar/pretty-env-logger/issues/34">#34</a>)</li>
<li><a href="cfad8e9445"><code>cfad8e9</code></a> Update Cargo.toml instructions in README.md (<a href="https://redirect.github.com/seanmonstar/pretty-env-logger/issues/32">#32</a>)</li>
<li>See full diff in <a href="https://github.com/seanmonstar/pretty-env-logger/compare/v0.4.0...v0.5.0">compare view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting ``@dependabot` rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- ``@dependabot` rebase` will rebase this PR
- ``@dependabot` recreate` will recreate this PR, overwriting any edits that have been made to it
- ``@dependabot` merge` will merge this PR after your CI passes on it
- ``@dependabot` squash and merge` will squash and merge this PR after your CI passes on it
- ``@dependabot` cancel merge` will cancel a previously requested merge and block automerging
- ``@dependabot` reopen` will reopen this PR if it is closed
- ``@dependabot` close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- ``@dependabot` ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- ``@dependabot` ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- ``@dependabot` ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
741: Docs 2 r=korken89 a=datdenkikniet
Working on the migration guide and other docs
TODO:
- [x] Migration guide
- [x] Hardcoded examples should link to example code that is tested (this was already done, AFAICT)
- [x] Address #699
- [x] Discuss: should we remove references to non-v2, apart from the migration guide and link to the book for v1? (Off-github conclusion: yes)
- [x] RTIC {vs,and} Embassy (important: distinction between embassy runtime & HALs)
- [x] More descriptive docs on how to implement & PR implementations of `Monotonic` to `rtic-monotonics`
Co-authored-by: datdenkikniet <jcdra1@gmail.com>
