Add WebAssembly-specific scheduler and update browserwasm condition#268
Merged
ChrisPulman merged 1 commit intomainfrom Sep 8, 2025
Merged
Add WebAssembly-specific scheduler and update browserwasm condition#268ChrisPulman merged 1 commit intomainfrom
ChrisPulman merged 1 commit intomainfrom
Conversation
Use WasmScheduler.Default for WebAssembly targets to handle lack of multithreading, and update the csproj condition for browserwasm to use EndsWith for better compatibility.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #268 +/- ##
========================================
- Coverage 5.47% 5.43% -0.04%
========================================
Files 16 16
Lines 712 717 +5
Branches 105 105
========================================
Hits 39 39
- Misses 669 674 +5
Partials 4 4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
glennawatson
approved these changes
Sep 8, 2025
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
update
What is the current behavior?
browserwasm uses TaskPoolScheduler.Default incorrectly
What is the new behavior?
Use WasmScheduler.Default for WebAssembly targets to handle lack of multithreading.
Update the csproj condition for browserwasm to use EndsWith for better compatibility.
What might this PR break?
N/A
Please check if the PR fulfills these requirements
Other information: