- 29 9月, 2012 6 次提交
-
-
由 Graydon Hoare 提交于
-
由 Tim Chevalier 提交于
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
- 28 9月, 2012 5 次提交
-
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
由 Graydon Hoare 提交于
-
- 27 9月, 2012 1 次提交
-
-
由 Patrick Walton 提交于
-
- 26 9月, 2012 1 次提交
-
-
由 Patrick Walton 提交于
-
- 24 9月, 2012 1 次提交
-
-
由 Brian Anderson 提交于
-
- 22 9月, 2012 1 次提交
-
-
由 Graydon Hoare 提交于
-
- 20 9月, 2012 6 次提交
-
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Graydon Hoare 提交于
-
- 19 9月, 2012 2 次提交
-
-
由 Brian Anderson 提交于
-
由 Patrick Walton 提交于
-
- 15 9月, 2012 3 次提交
-
-
由 Graydon Hoare 提交于
-
由 Patrick Walton 提交于
-
由 Patrick Walton 提交于
-
- 13 9月, 2012 1 次提交
-
-
由 Patrick Walton 提交于
-
- 12 9月, 2012 1 次提交
-
-
由 Brian Anderson 提交于
-
- 11 9月, 2012 2 次提交
-
-
由 Brian Anderson 提交于
-
由 Niko Matsakis 提交于
The Mut<T> type is intended to allow freezable data stuctures to be stored in `@mut` boxes. Currently this causes borrowck to be very conserivative since it cannot prove that you are not modifying such a structure while iterating over it, for example. But if you do `@Mut<T>` instead of `@mut T`, you will effectively convert borrowck's static checks into dynamic ones. This lets you use the e.g. send_map just like a Java Map or something else.
-
- 10 9月, 2012 1 次提交
-
-
由 Brian Anderson 提交于
-
- 08 9月, 2012 1 次提交
-
-
由 Elliott Slaughter 提交于
Safe points are exported in a per-module list via the crate map. A C runtime call walks the crate map at startup and aggregates the list of safe points for the program. Currently the GC doesn't actually deallocate memory on malloc and free. Adding the GC at this stage is primarily of testing value. The GC does attempt to clean up exchange heap and stack-allocated resource on failure. A result of this patch is that the user now needs to be careful about what code they write in destructors, because the GC and/or failure cleanup may need to call destructors. Specifically, calls to malloc are considered unsafe and may result in infinite loops or segfaults.
-
- 04 9月, 2012 1 次提交
-
-
由 Patrick Walton 提交于
-
- 03 9月, 2012 3 次提交
-
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
- 31 8月, 2012 1 次提交
-
-
由 Brian Anderson 提交于
-
- 30 8月, 2012 2 次提交
-
-
由 Patrick Walton 提交于
-
由 Graydon Hoare 提交于
-
- 29 8月, 2012 1 次提交
-
-
由 Graydon Hoare 提交于
-