This would be a good question category for next year's [Community
Survey](https://nim-lang.org/blog/2018/10/27/community-survey-results-2018.html):
* In which
[major](https://en.wikipedia.org/wiki/Globalization_and_World_Cities_Research_Network#2018_city_classification)
world city are you
> Be aware of Djikstra's opinion on ranges: >
> [https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html](https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html)
Oh not that again. Exclusive ranges ONLY work when you have a sentinel value
that shouldn't be
Regarding lazy ranges, @timotheecour was interested in implementing D ranges in
Nim, see
[https://github.com/timotheecour/vitanim/tree/master/drange/src/drange](https://github.com/timotheecour/vitanim/tree/master/drange/src/drange).
I often struggled with the same need, Nim offers genericHead
Use this:
array[MSA_BASE_GROUP_LEN, align_tag_col_t]
Run
(This is difficult to search for, so I thought I should ask the question.) I
see this warning:
.nim(101, 23) Warning: < is deprecated [Deprecated]
base*: array[0 ..
This turned out to be an unrelated problem.
However, I did find a problem with relative imports here:
[https://github.com/c-blake/cligen/issues/88](https://github.com/c-blake/cligen/issues/88)
That one is easy to work around, and might be a mistake by the user anyway.
But I do wonder how
Sadly I cannot maintain it much, but shameless plug ahead:
[https://github.com/Araq/lexim](https://github.com/Araq/lexim)
Lexim compiles regular expressions into no-overhead Nim matching code and can
be used with lexbase.
I'd love to help but I need more information. What version of Nim do you use?
0.19.9 has a known bad regression wrt `gensym` in templates that we're working
on but 0.19.4 should not be affected.
Interested as well
Not sure if it is right or wrong, Option lifts its equality from the user
supplied one because that's generally the right thing to do. But please report
this issue on github so we can track its progress/conclusion.
@yglukhov Still better than nothing and one can always align the C file
versions.
@CavariuX Edit `compiler/extccomp.nim` (External C compiler invokations).
Nimx also uses it's own [inlined version of
stb_image](https://github.com/yglukhov/nimx/blob/master/nimx/load_image_impl.nim),
but it inlines it with `#define STB_IMAGE_STATIC`, so that C symbols remain
hidden, and only nim symbols are visible and get their proper mangling. The
most proper way
I've spent sometime making the `lexbase` version:
[https://gist.github.com/alaviss/83a48f0344d55efbebcca3bce35e4157](https://gist.github.com/alaviss/83a48f0344d55efbebcca3bce35e4157)
This beast has ~310 LoC, so it's just ~100 LoC more than your `re` version :)
After writing mine, I noted a few
13 matches
Mail list logo
