Skip to content

Conversation

@AshleighAdams
Copy link
Owner

This is to allow the scheduler to ensure you're within an expected execution context, without needing to force a yield if you're already in the expected or desired context

This includes major refactoring to collapse the implementation into Scheduler for simplicity. Added unit tests to check behavior of Marshal() and Yield() with respect to threads and the sync context

High level of what was changed, possibly include why this approach was taken.

Are there any concerns or areas to be aware of regarding the approach taken or areas changed?

  • Tests added

@AshleighAdams AshleighAdams self-assigned this May 22, 2025
@AshleighAdams AshleighAdams added the enhancement New feature or request label May 22, 2025
This is to allow the scheduler to ensure you're within an expected
execution context, without needing to force a yield if you're already
in the expected or desired context

This includes major refactoring to collapse the implementation into Scheduler
for simplicity. Added unit tests to check behavior of Marshal() and Yield()
with respect to threads and the sync context
@AshleighAdams AshleighAdams merged commit a89ede9 into master May 22, 2025
2 checks passed
@AshleighAdams AshleighAdams deleted the marshal branch May 22, 2025 01:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants