Move newThread from the processor namespace (multi/processor) into the thread namespace #35

New Issue

2022-02-04T17:33:11-05:00

rayaman commented

2022-02-04 17:33:11 -05:00

(Migrated from github.com)

This change is rather large and the main issue would be pumping the events. On surface level I could have all processors pump the thread scheduler regardless of where they are. ~~Might not be too difficult to do that. Either way this will not be coming out until version 16.x.x since it's a major change.~~ Change ended up not being too difficult.

This change is rather large and the main issue would be pumping the events. On surface level I could have all processors pump the thread scheduler regardless of where they are. ~~Might not be too difficult to do that. Either way this will not be coming out until version 16.x.x since it's a major change.~~ Change ended up not being too difficult.

rayaman commented

2022-02-05 00:19:39 -05:00

(Migrated from github.com)

This was changed and a proxy was made for multi:newThread to thread:newThread so no changes have to be made on your end. ~~However, threads on a processor that is paused will still run!~~

This was changed and a proxy was made for multi:newThread to thread:newThread so no changes have to be made on your end. ~~However, threads on a processor that is paused will still run!~~

rayaman commented

2022-02-10 09:27:04 -05:00

(Migrated from github.com)

Threads on a processor that is stopped/paused will also halt! If you want a thread that is independent to what the processor is doing create it using thread:newThread(...)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: epicknex/multi#35