Intriguing...
I googled a bit to check what this was about and found:
- pseudo-reloc.c, the part of mingw handling pseudo-relocations =
http://www.oschina.net/code/explore/mingw-runtime-3.18-1/pseudo-reloc.c
- the patch for pseudo-reloc v2 support =
Hi everyone,
I've been tossing around an idea for a library utility designed to make
unique pointers easier to use, especially for balanced binary search
trees and the like. The core of the idea is that I conjecture it's safe
to temporarily violate linearity *while the locations in question
I just tested this in my code, it solved a sticky problem I had with
updating owned data nested deep inside a tree-ish container. My original
solution wasn't very nice (it just compromised on efficiency and copied too
much data around). The new code is shorter and more efficient (no copies!
yey!).
On 8/30/13 3:39 PM, Patrick Walton wrote:
Thoughts? Does this seem useful? Are there soundness issues I didn't
notice?
Brian pointed out a massive soundness hole in this, unfortunately. The
problem is that you can read from the original locations; the right to
read is not shut off during the
Sigh, I guess it was too good to be true :-(
I'd settle for the ability to say: update_in_place(foo.owned_pointer,
fn(~T) - ~T) - surely this would be safe?
Speaking of which, a secondary problem I encountered when doing this sort
of thing, is the Once function issue listed in
On 08/30/2013 05:05 PM, Graydon Hoare wrote:
Hi,
As I'm sure many of you who know me are aware, my role as technical
lead on Rust has been quite draining over the years. Both to myself
and to those I've worked with, it just isn't a great fit for me.
In recognition of this, I am stepping
Graydon,
So what does not drain you ? What kicks you into high gear and keeps you
salivating for more ?
Many of us do not know you personally, and knowing a bit more about what
really interests you, would open a few of our eyes on the list.
(thanks for your efforts)
On Fri, Aug 30, 2013 at
