The link I provided in my first post allows you to read/download it free from
my Scribd site. Here it is again.
[https://www.scribd.com/doc/228155369/The-Segmented-Sieve-of-Zakiya-SSoZ](https://www.scribd.com/doc/228155369/The-Segmented-Sieve-of-Zakiya-SSoZ)
I've tested it many times, and there
Can you put the paper on a link that is not behind a paywall? I am normally
pretty trained to port from different languages to different languages, but
from the paper I can't do copy paste at all.
Thanks. I'm in the process of learning enough Nim to take on this effort.
However, I would do what you were thinking, and first try a comparable direct
C++ to Nim translation, just to get something to work. But it's going to be
some time (with my time/learning curve constraints) to create someth
Honestly, this sounds like an interesting little project to bang out. However,
I must admit that I am a humble Web Developer and, by extension, am not well
versed in mathematics.
The best I could do is translate your C code in the linked document into Nim
and maybe make a few small changes. How
It would be nice to have though... I have take the liberty to open [Issue
#6201](https://github.com/nim-lang/Nim/issues/6201) on GitHub.
Special thanks to `stisa` for doing the initial work in identifying where we
needed to modify the standard library to get the very first `nim` build on
Android.
Thanks also to `TiberiumN` for helping me test run nim on 64-bit ARM.
With [GitHub Pull Request #5772](https://github.com/nim-lang/Nim/pull/5772)
merged, proper support for the Android operating system is coming to the next
version of Nim.
Yes, Android is very similar to linux, but in some cases it's doing its own
thing. That's why we introduced an own OS symbol
The usual TR macro problem is "ugh, not applied in this case because of sublte
AST differences". The dreamed up problem by people who never use them is "ugh,
the transformation introduced bugs".
I'm happy to reconsider my opinion when real bugs resulting from TR macros are
reported.
it's not talked about that much, since it _very_ useful but only in a few
contexts. And it's also probably the best way to shoot yourself in the foot in
the whole language.
I think a set of macros implementing regular old OOP (and maybe methods too )
should probably go into the standard library. This may require the ability to
call macros in a few new ways though.
10 matches
Mail list logo