The main reason that I did not use the bitv logic was because I wanted
to allocate the entire set of bit vectors in one allocation. Also: I
am in the process of rewriting dataflow to make use of a graph and be
more reusable, so please do not modify it without discussing with me
first.
Niko
On We
On Sun, May 5, 2013 at 2:16 AM, Brian Anderson wrote:
> On 05/03/2013 09:24 PM, Thad Guidry wrote:
>>
>> Looks like libuv is a showstopper currently for me on Windows Cygwin
>> building.
>>
>> Why is it used ? Should it be ? Will it be in the future ?
>>
>> Can someone throw up a quick paragraph
On 13-05-07 09:49 AM, Mikhail Zabaluev wrote:
> What do you think of using Rust lambdas for context-sensitive
> translations? That could easily accommodate any sort of variance, and
> would not complicate the fmt! syntax (though it would require another
> fmt-like macro to substitute, as well as m
Timely bug: today's explanation of the Diablo3 gold-duping market
crash. http://pastebin.com/YYPM4uQK
On 4/29/2013 10:43 PM, Jack Moffitt wrote:
For the most part, nobody checks. They weighed the cost of those errors
against the potential performance loss and decided they would prefer to
go fa
I was just going to post that as well. This is also exactly the kind
of thing that checked arithmetic performance would not be an issue
for.
jack.
On Wed, May 8, 2013 at 4:33 PM, Ben Lerner wrote:
> Timely bug: today's explanation of the Diablo3 gold-duping market crash.
> http://pastebin.com/YY
On 13-05-07 09:12 AM, Sanghyeon Seo wrote:
> I asked about this in January
> https://mail.mozilla.org/pipermail/rust-dev/2013-January/002879.html
> and was told 1) request logging was disabled 2) it will probably not be
> interesting before the next release.
>
> It has been a month since 0.6 relea
On Tue, May 7, 2013 at 12:01 AM, James Tranovich
wrote:
> Hello all,
>
> What can I do to help make rusti "halfway tolerable"?
>
> Not to belabor the point, but rusti definitely needs some love -- my git
> version of rusti as of one or two days ago always crashes with
> "memory_region::~memory_reg
