Suzu/suzu-next
1
0
Fork 0
Code Issues 7 Pull requests Projects 5 Releases Packages Wiki Activity Actions

Prevent concurrent no_std runtime calls via atomic switch #4

New issue
Open
opened 2026-01-05 16:32:45 -05:00 by yukirij · 0 comments
yukirij commented 2026-01-05 16:32:45 -05:00
Owner
Copy link

As no_std versions of the library can panic upon concurrent access, an atomic value should be used to return error conditions when the runtime is performing operations.

As no_std versions of the library can panic upon concurrent access, an atomic value should be used to return error conditions when the runtime is performing operations.
yukirij added this to the Sandbox milestone 2026-01-05 16:33:46 -05:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Bug

Not working as expected

  
Design

Plan implementation

  
Feature

New functionality

  
Improvement

Change to existing functionality

  
Investigate

Needs more information

  
Suggestion

Idea for consideration

  
Triage

Look into potential issue

  
Bug

Not working as expected

  
Design

Plan implementation

  
Feature

New functionality

  
Improvement

Change to existing functionality

  
Investigate

Needs more information

  
Suggestion

Idea for consideration

  
Triage

Look into potential issue

No labels
Bug
Design
Feature
Improvement
Investigate
Suggestion
Triage
Bug
Design
Feature
Improvement
Investigate
Suggestion
Triage
Milestone
Clear milestone
No items
No milestone
Sandbox
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Suzu/suzu-next#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?