Created
September 26, 2012 17:46
-
-
Save awreece/3789458 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<areece> I've asked a couple of times but wanted to ask a different group: does rust use a custom llvm or can it be linked against the latest llvm release? | |
<pcwalton> areece: it's custom | |
<areece> (alternatively, how do I ask the mailing list) | |
... | |
<pcwalton> depends on some GC changes that we haven't upstreamed | |
<areece> pcwalton: so how will it fail if I don't use the custom llvm? | |
<areece> will it just subtly fail eventually? | |
<areece> because it builds successfully | |
<bstrie> it might not fail at all if gc isn't enabled | |
<pcwalton> if you don't use the GC I think it might well work | |
<pcwalton> the normal behavior is not to use the GC | |
<pcwalton> it's experimental and doesn't pass all tests yet | |
<pcwalton> the precise GC, that is | |
... | |
<bstrie> areece: currently heap-allocated types use ref counting rather than gc | |
<bstrie> so you can still heap-allocate | |
<bstrie> but I don't think there's a cycle collector | |
<areece> hrm | |
<bstrie> at least not since yesterday :) | |
... | |
<areece> so moral of the story is it will fail if I do something interesting in some cases? | |
... | |
<areece> and by fail, it just won't gc | |
... | |
<bstrie> areece: if you avoid compiling anything with the experimental gc flag, I think you should be okay |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment