Leandro Ostera
Leandro Ostera
At the moment we use Atomic, Mutex, and Weak throughout the Riot runtime to do synchronization of work across the schedulers. This style of programming doesn't play very well with...
When running on a large number of cores, the current process stealing starts dead-locking schedulers and shows a few other bugs: * a process gets queued up in several schedulers,...
At the moment we are exposing our internal "Dashmap" as a Hashmap that should be prefered in userland Riot programs for concurrent access. Sadly, this Hashmap is far from ideal...
In many cases we want to execute some work that does not play well with Riot's scheduling, that wouldn't play well with work-stealing, that needs to use libraries that don't...
At the moment refs are used in a few places like Mint Tea but there's no good explanation of what they are. We should add a little example and document...
At the moment only TCP sockets are nicely supported, but I've had folks reach out with UDP use-cases so it'd be a good idea to at least have basic support...
Would be useful to have a little File module to read/write files in a scheduler-friendly way. In short, we would need a module _like_ `Net.Socket` with functions like: * `File.open...
**Definition of Done** * Every major version of a package in the index that successfully compiles will have its corresponding generated documentation published under `https//reuniverse.github.io/packages///` **What has to be done**...
**Definition of Done** * We can search for packages in the index at [Reuniverse](https://reuniverse.github.io/) by name, description, target platform, tags. * Searching should handle any amount of packages that we...
**Definition of Done** - [X] We can publish a index of Reason packages to a public url - [ ] The index is updated periodically. - [ ] Document how...