Brad, > Sorry not to have been sufficiently clear that the bigint range support > was only on a branch so far, and not yet on master. Since sending that > mail, I've pushed that branch forward a bit and made it better, but am > also running into a memory corruption error that likely has its cause in > the BigInteger module itself (and I'm now just pushing it hard enough to > trip over it).
No problem. I failed to investigate your branch over the last few days, long (and boring but true) story. I can however do stuff with it this week and next, so I can actas a bit of a tester. > Too bad that this isn't something you'd benefit greatly from, but I'll > continue to push it forward in my spare time in hopes of getting it into > this fall's release. Slight misunderstanding. My factorial and fibonacci implementations depend on the bigint type – I have a GitHub repository of these functions done properly (none of this int/long broken implementation stuff :-) ) with tests in many languages. The Rosetta Code examples are usually int/long and never have any tests. I used my implementations really to test out example-based and property-based test frameworks for the various languages basically to see which languages cared about testing and which just bluffed. What I was saying is that I do not have any serious Chapel applications that are blocked on this feature. For this reason there is no rush. However, the codes I do have are blocked on the problem in some sense – i.e. the implementations using while rather than for with range are ugly. And the lack of consistency of operators on integer-like types is, in my view, wrong. I have this problem with D and Kotlin as well as Chapel. ;-) Can you resend the details of the repository and branch with this in and I will pull the branch into my clone of master and have a play. -- Russel. =========================================== Dr Russel Winder t: +44 20 7585 2200 41 Buckmaster Road m: +44 7770 465 077 London SW11 1EN, UK w: www.russel.org.uk
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
