After playing a bit around, I think Araqs solutions is the better one ^^. But
now I need a way to get the types of the arguments of a procvar in a macro. Is
this possible?
@andrea Yes, I think you understand me, the alphabet of DNA and RNA can and
should be represented with two bits per character. There's a
['standard'](https://genome.ucsc.edu/goldenpath/help/twoBit.html) for storing
FASTA files as .2bit files for compression, but I am befuddled as to why they
> I know Nimoy, but it isn't suitable for my project because it creates threads
> in the background.
actually it uses an abstract Executor which as a default implementation happens
to uses threads
> Also it has the same problem as almost every event system I saw, it requires
> to wrap the
> Why not to use pointer instead of array[8, byte]. Will Work for both 64 and
> 32 bits.
Yes, of course this is much better
> Why not use closures to hide the differences in parameters that the procs
> take?
The problem with this method is that I would have to write one macro for
wrapping
@cdunn2001 Thank you. I am no bioinformatician myself, but I am trying to learn
some of the standard algorithms as they may have applications elsewhere. Hope
Cello turns out to be useful, though!
@bpr If you see [here](https://github.com/unicredit/cello#wavelet-tree), one
can turn a string
Wow, this is really great! Do you support the 2 bit representation for DNA/RNA
sequences? I looked and didn't see it.
I think writing tools for genome assembly in Nim would be worthwhile.
Bioinformaticians use Python a lot but of course need to write fast code in C
and C++. Nim's Pythonesque
Why not to use `pointer` instead of `array[8, byte]`. Will Work for both 64 and
32 bits.
This is really good. Forked into bio-nim. You're welcome to join that GitHub
org with me and bpr, if you want.
* [https://github.com/bio-nim](https://github.com/bio-nim)
> I have ~/bin in my path and put the symlinks there.
This is exactly what I'm doing when adding things in Linux.
