priority-queue
Here are 341 public repositories matching this topic...
-
Updated
Apr 16, 2020 - TypeScript
-
Updated
Apr 3, 2020 - Java
-
Updated
Apr 21, 2020 - JavaScript
It appears that the documentation of FastPriorityQueueNode.Priority is from some previous version as it talks about setting the Priority in the constructor of the node, and yet FastPriorityQueue.Enqueue now has the priority as a parameter, so it seems wrong for the node to be setting anything, and sure enough, the example doesn't.
Is it the example or the Priority documentation that is misleadi
-
Updated
Apr 21, 2020 - JavaScript
-
Updated
Oct 16, 2019 - Swift
-
Updated
Mar 12, 2019 - Go
-
Updated
Aug 18, 2019 - JavaScript
-
Updated
May 8, 2019 - JavaScript
-
Updated
May 21, 2020 - C
-
Updated
Jul 1, 2018 - Java
-
Updated
Mar 14, 2020 - TypeScript
-
Updated
Jul 11, 2019 - C
The documentation link at the bottom of the readme page seems to jump to a local up address. I think maybe needs updating?
-
Updated
Aug 15, 2019 - Python
-
Updated
Apr 27, 2020 - JavaScript
-
Updated
May 8, 2020 - Java
-
Updated
Nov 16, 2019 - JavaScript
-
Updated
Jul 11, 2016 - Python
-
Updated
May 22, 2020 - Jupyter Notebook
-
Updated
Mar 28, 2018 - Swift
-
Updated
Mar 29, 2020 - Rust
-
Updated
Jun 2, 2017 - C
Currently, we post new job to balancer and wait on the request CompletedChannel from the user side, like this:
balancer.PostJob(request)
<-request.CompletedChannel
We should merge this together and have one method, which will either:
- Fail immediately if the request validation fails
- Block for the whole duration of the job, meaning the method should do the wait on the CompletedCha
-
Updated
May 27, 2018 - Java
-
Updated
Jan 31, 2020 - Java
-
Updated
Nov 21, 2019 - C++
Improve this page
Add a description, image, and links to the priority-queue topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the priority-queue topic, visit your repo's landing page and select "manage topics."
It would be really cool to have the documentation on each method/event that we can use. We can look into README.md for that, but I think it'll be way more better if we had the separate page that describes each API method/event that we can subscribe to, what arguments it accepts, what does it return, how it works, which errors can it throw etc.
This could be implemented by using the Github Wiki,