Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/generic queues #1

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Conversation

PanopticaRising
Copy link
Collaborator

No description provided.

… constructors.

Alone, this does nothing, but a future commit will expand on this and allow `acquire` to take a data or priority argument that can be operated on by a queue's comparator.
…er as an array or custom Queuelike object, does not break existing Semaphore and Mutex functionality.

This also adds the tinyqueue library and a class wrapper as an example of a custom Queuelike object. Currently, these act as standard arrays, but a future commit will expound on tagging priorities to the QueueEntrys.
PanopticaRising and others added 3 commits March 5, 2021 00:32
This changed from never to void because void is the absense of an
argument. This makes type guarantees a little cleaner.

test: Added a test for TinyQueue's implementation to verify that custom
queue logic holds up.
…ially still needs fixes for tryAcquire. Needs tests for withTimeout.
fix: Fixed default typings on the Semaphore.
@PanopticaRising PanopticaRising marked this pull request as ready for review March 8, 2021 22:22
@@ -0,0 +1,4033 @@
{

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why didn't this have a package-lock.json? is it because they use yarn?

@@ -13,7 +13,8 @@
"noImplicitAny": true,
"noImplicitReturns": true,
"noUnusedLocals": true,
"allowSyntheticDefaultImports": true
"allowSyntheticDefaultImports": true,
"esModuleInterop": true

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing tsconfig seems more sensitive and more likely to not be accepted upstream, what do we gain from this configuration?

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.

2 participants