nim-taskpools
RFCs
| nim-taskpools | RFCs | |
|---|---|---|
| 2 | 34 | |
| 100 | 135 | |
| - | 1.5% | |
| 4.6 | 4.2 | |
| 3 months ago | 11 months ago | |
| Nim | ||
| GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nim-taskpools
-
Nim version 2.0.0 release candidate
No, not directly but Nim supports async. Effectively it turns the function into an Iterator whose state can be passed around. Those are put into Futures.
Its possible to write your own async engine, or you could use the iterator yourself if you really wanted. It's actually not too hard.
Checkout: https://github.com/status-im/nim-taskpools
- Nim-taskpools: Lightweight, energy-efficient, easily auditable threadpool
RFCs
- Nim Sum types, 2024 variant
- Nim Roadmap 2024 and Beyond
- Nim v2.0 Released
-
Contribute to the Python-like Nim language
compiler support for object construction shorthand
-
Nim 2.0.0 RC2
Well, maybe not writing. Occasionally low-level C libraries - especially those that deal with keyboard input - decide to provide identifiers differing only in case... There's a WIP RFC for providing a way to deal with identifiers that need to be verbatium by surrounding them with backticks, though.
https://github.com/nim-lang/RFCs/issues/477
- please comment on "It totally sounds like the n-word" as well
- Nim goto intermediate representation (NGIR)
-
My Nim Development Weekly Report (3/12)
Following The Roadmap 2023 for community building , you could join us in the matrix space where we discuss how to build a community. We appreciate doable suggestions and helps, such as improving the workflow, implementing the roadmap, suggesting doable tasks, reviewing code from contributors. United we stand. We shall work together to make the community thrive.
- Nim Roadmap 2023
-
My Nim Development Weekly Report (2/19)
First of all, the Nim development follows The Roadmap 2023, which specifies what features might be implemented or removed in 2023. As we can see, completing incremental compilation and recursive module dependencies might be the most important tasks to be done in 2023. You might subscribe to the roadmap and write down your expectations of Nim in 2023 there.
What are some alternatives?
hello_musl - NimScript (config.nims) for building a static binary using Nim + musl + pcre + libressl/openssl
nimskull - An in development statically typed systems programming language; with sustainability at its core. We, the community of users, maintain it.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
nimforum - Lightweight alternative to Discourse written in Nim
vala-www - Website of the Vala programming language
nim-chronos - Chronos - An efficient library for asynchronous programming
mummy - An HTTP and WebSocket server for Nim that returns to the ancient ways of threads.
shady - Nim to GPU shader language compiler and supporting utilities.
cligen - Nim library to infer/generate command-line-interfaces / option / argument parsing; Docs at
futhark - Automatic wrapping of C headers in Nim
nephyr - Nim wrapper for Zephyr