haxscramper

5 ms·

1.
by haxscramper 4y ago
As someone who has been writing nim for many years now, using grep, rg, and various other search tools I can say that I've never had any issues with finding things I wanted. This is just one of those imagined issues that your realize d
2.
by haxscramper 4y ago
This is not really true, most of the times the discussion goes like this Q: "Why haven't you implemented feature X -- python has it, so nim should too" A: "Nim is not python, it is a different language, not all things im
3.
by haxscramper 4y ago
Somehow I missed this (very noticeable actually) non-algorithmic toggle button until I saw your comment, so many thanks for mentioning this.
4.
by haxscramper 4y ago
Right now we are not forking "the language" as a collection of ideas etc. as you seem to think. Instead we are doing a much simpler thing - we are forking "the code". Of course former is built on latter, but current focu
5.
by haxscramper 4y ago
On how: The "method" is to just respect the future contributors from the start, instead of waiting for ten years until someone tells you to write better messages. Why can't it be applied: no idea, writing sensible commit mess
6.
by haxscramper 4y ago
That does not magically rewrite all previous commit messages, although apparently the improvement is present https://github.com/nim-lang/Nim/commits?author=Araq - most of the total ~25 comments made in the last se
7.
by haxscramper 4y ago
Commits message guidelines are a part of the contribution guidelines and are available in the documentation (linked in the GitHub page). Concrete application of said guidelines can be seen in the commit message history.
8.
by haxscramper 4y ago
There is no singular "story" here, mostly several former contributors decided for one reason or another (of course there are a lot of small "stories" behind this, but writing them all down would just come out as being &q
9.
by haxscramper 4y ago
We are certainly not opposed to this, although some of the more fundamental structural changes in the codebase might temporarily hurt the stability - this was one of the friction points with the mainline. While stability is important it was
10.
by haxscramper 4y ago
That is a correct interpretation, we decided some humor won't hurt at the start, and it certainly wasn't as venomous (aka "death to nim") as parent comments suggested
11.
by haxscramper 4y ago
!: this is mostly a personal note although I am one of the nimskull contributors For now the aim of this project is first and foremost refactoring and making it easier to contribute and improve the main code base of the compiler, as indica
12.
by haxscramper 5y ago
I think better phrasing would indeed be something like "several former core developers" - of course we can't really measure up to the size of the original community, and don't yet have any paid developers (like Araq and
13.
by haxscramper 5y ago
Actually the phrasing in the readme is not correct - I will change it later, but now I want to say that the objective is not deleting "much" of it, but rather cleaning up old and deprecated modules, or providing alternative soluti
14.
by haxscramper 5y ago
No, never. Actually the most problem I've ever had with this feature is seemingly unending discussions that come up in almost every single HN discussion ever, like https://news.ycombinator.com/item?id=28651040 > wo
15.
by haxscramper 5y ago
I can't remember exact place where I've seen this discussion (I think it was on the nim IRC), but if I recall correctly, the original line of thought with nim was to take C (because fast/compiled/available-everywhere) an
16.
by haxscramper 5y ago
Adjacent comment already has a list of concrete libraries/frameworks for large number of areas, so I just want to mention that nim has a very good metaprogramming capabilities, and if the /language/ itself does not feel up to
17.
by haxscramper 5y ago
This way you can write json literals in the code, and it will look just like regular json. For serialization and deserialization stdlib uses `to/load/store` proc names. import std/json echo %*{ "key1": &q
18.
by haxscramper 5y ago
It does affect identifiers, built-in keywords and type names in the same manner, though it is completely beyond me why anyone would write 'tY_PE Position = tUPLE[x, y: iNt]'. If we are going to dismiss any nontrivial behavior as &
19.
by haxscramper 5y ago
Another nim & python thread that has not been mentioned yet here https://news.ycombinator.com/item?id=28506531 - project allows creating pythonic bindings for your nim libraries pretty easily, which can be useful if y
20.
by haxscramper 5y ago
> Do you enjoy the tabs vs spaces debate? How about single quote Vs double quotes? Ugly inconsistently styled code? Nim solved tabs/spaces debate by allowing only spaces. Single/double quote are also completely separate, so the
21.
by haxscramper 6y ago
While I don't claim to have a comprehensive numbers, I did a quick `rg` on a full clone of nimble package list, and found that macros constitute approximately 0.4% of all definitions (functions, procedures, templates, methods). pro
22.
by haxscramper 6y ago
Using nim pattern matching library to implement simple dataflow programming DSL.
23.
Patten Matching in Nim(nim-lang.org)
145 points by haxscramper 6y ago|50 comments