Hi Russel --
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.
I wouldn't spend too much time kicking the tires (or tyres) until I get
past this memory corruption error. I'll give you a heads-up once I do and
would be happy for help testing at that point, though!
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. ;-)
Got it, cool!
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.
This is the branch:
https://github.com/bradcray/chapel/tree/bigint-ranges
but again, please feel encouraged to hold off until I can get rid of the
memory corruption because it results in unpredictable behavior and so will
only vex you if you run into it (though I suppose if you don't, we can
claim a partial victory...).
-Brad
------------------------------------------------------------------------------
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
