Skip to content

fix edition 2024 unsafe link section #1055

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.

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Ddystopia
Copy link
Contributor

In edition 2024, we must use #[unsafe(link_section = ...)] instead of #[link_section = ...]. But rtic_macros is only checking for #[link_section = ...].

  • fix: in edition 2024 link_section is used as unsafe(link_section = ...)
  • chore: changelog entry

Comment on lines 10 to +12
- Adapt `slic` backends to new version with `mecall`
- Allow software tasks to be diverging (return `!`) and give them `'static` context.
- Fix: supoort edition 2024 `unsafe(link_section)` attribute
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Adapt `slic` backends to new version with `mecall`
- Allow software tasks to be diverging (return `!`) and give them `'static` context.
- Fix: supoort edition 2024 `unsafe(link_section)` attribute
- Fix: supoort edition 2024 `unsafe(link_section)` attribute
- Adapt `slic` backends to new version with `mecall`
- Allow software tasks to be diverging (return `!`) and give them `'static` context.

@AfoHT
Copy link
Contributor

AfoHT commented Apr 16, 2025

Really nice you spotted it and got it sorted! Thank you 🚀

Would be amazing if this could be caught in the future with some UI test or similar, something you could look into perhaps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants