loci

It means Loci will perform similarly to C and C++, not that C and C++ have some particular overhead that Loci doesn't.

The author has a nice piece in the documentation regarding how dynamic dispatch is implemented in loci in order to support structural typing.

There are 18 loci on 15 chromosomes that are associated with myopia.

Yeah, I've messed around with Method of Loci off and on over the years, but it hasn't done much for me.

I have a hard time believing that large pharma research labs are limiting themselves to single loci for a given disease phenotype.

DNA testing may be theorethically sound, but in practice it's restricted to testing about 13 different loci, which is a miniscule porton of the actual information at hand.

I'm curious, Have you done any experimentation with Method of loci?

>There are 18 loci on 15 chromosomes that are associated with myopia.

This happens because differences in the frequency of alleles at different loci are correlated across populations — the alleles that are more frequent in a population at two or more loci are correlated when we consider the two populations simultaneously.

I've considered adapting the method of loci to an audible equivalent (attaching memory to audible cues in a soundscape), but I tend not to wander through soundscapes in my mind...

Its not surprising that people whom are passionate about their circle of competency, those who would venture in all directions from their initial locus/loci, seemingly random areas would pick up observations that others miss.

There isn't a central authority because there doesn't need to be: as Foucault might argue, there are merely different loci of power or force that tend to create webs of what is acceptable or not in a given situation.

The method of loci, for building/encoding hierarchical "memory palaces", works well for remembering key ideas or facts and building upon them to compose your models.

I personally knew the method under the name "memory palace" but not "memory of Loci".

Memory has always been an interesting topic to me, and the "method of loci" as described in the article is something that fascinates me, particularly because I've never been able to really do it (not for lack of trying).

Yes, this is true; the point was to highlight more generally the complexity of ensuring correctness when moving/copying C++ objects versus doing the same thing in Loci.

I've come to like the C compatibility in Julia and Rust (and I'm sure I'll come to like the C compatiblity in Loci, too), but the relative lack of C++ interface support (something that I know Julia's been working on, at least based on what I've seen on the mailing lists) has been a bit of a sore point for integrating with C++ projects.