Our great sponsors
| patty | gara | |
|---|---|---|
| 3 | 1 | |
| 263 | 100 | |
| - | - | |
| 2.1 | 10.0 | |
| about 1 year ago | almost 4 years ago | |
| Nim | Nim | |
| Apache License 2.0 | MIT License |
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.
patty
-
Removing Garbage Collection from the Rust Language (2013)
This comment is misleading &| misinformed.
Sum types are built-in [1] for formal parameters. `nil` is only for `ref|ptr` types. In much code you can just use stack allocated value types and there is neither GC concern nor nil concern, but there is also a mode to help: https://nim-lang.github.io/Nim/manual_experimental_strictnot...
Nim has an easy-ish to use Lisp-like syntax macro system where you just receive & process an AST. So, to do the rest you can make libraries adding the feature without relying upon upstream compiler: such as https://github.com/beef331/sumtypes for variables with sum types or pattern matching libs like https://andreaferretti.github.io/patty/ | https://github.com/alehander92/gara.
- What would be your “perfect” programming language?
-
Patten Matching in Nim
...except that macros don't change the syntax of the language! They just offer convenience on top of it, most common example is the `=>` lambda operator from the `sugar` module. I do agree, that the pattern matching macro presented in the article is a bit hard to get used to, but you don't have to, if you don't like pattern matching. And of course there are plenty of alternatives available as well, the simplest one imo is https://github.com/andreaferretti/patty
gara
-
Removing Garbage Collection from the Rust Language (2013)
This comment is misleading &| misinformed.
Sum types are built-in [1] for formal parameters. `nil` is only for `ref|ptr` types. In much code you can just use stack allocated value types and there is neither GC concern nor nil concern, but there is also a mode to help: https://nim-lang.github.io/Nim/manual_experimental_strictnot...
Nim has an easy-ish to use Lisp-like syntax macro system where you just receive & process an AST. So, to do the rest you can make libraries adding the feature without relying upon upstream compiler: such as https://github.com/beef331/sumtypes for variables with sum types or pattern matching libs like https://andreaferretti.github.io/patty/ | https://github.com/alehander92/gara.
What are some alternatives?
nimble - Package manager for the Nim programming language.
samsara - a reference-counting cycle collection library in rust
Kind2 - A next-gen functional language [Moved to: https://github.com/Kindelia/Kind]
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).
sumtypes - Easy to use Nim sum type library
nitter - Alternative Twitter front-end
union - Anonymous unions in Nim
nimlings - Learn the Nim programming language by fixing tiny broken programs.
hebigo - 蛇語(HEH-bee-go): An indentation-based skin for Hissp.
macro-lisp - Lisp-like DSL for Rust language