Skip to content

Conversation

@ire4ever1190
Copy link
Owner

Small cleanup to internals. Fixe #7

Exposes newSchedulerBase which allows for restricting the proc type to how you want it (This then allows for restricting effects, exceptions, etc).

The start is then broken up into async/sync version (there were a lot of when statements anyways). This is to get around multisync needing me to specify the two different versions which locked the tasks being non gcsafe (Since thats what the types were specified as).

Want to clean up the code a bit more first though

Issue was in `start` that since I had already restricted `T` to the two kinds of handlers (To make multisync work) it didn't allow the gcsafety to pass through

Might need to make my own multisync
By not restricting it we can make it extend to gcsafe procs also
Needed to export the proc (maybe this is a good use of typebound ops?)
Bug is fixed on devel so at some point we can remove the strange code and just bump the min version
@ire4ever1190 ire4ever1190 linked an issue Feb 1, 2025 that may be closed by this pull request
@ire4ever1190 ire4ever1190 merged commit dd152ce into master Feb 1, 2025
3 checks passed
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.

start isn't gcsafe

2 participants