- 03 4月, 2013 6 次提交
-
-
由 Daniel Micay 提交于
-
由 bors 提交于
This pull request completely removes Mut<T> and the associated file (libcore/mutable.rs). Some minor changes were made to workcache (libstd/workcache.rs) as it was using Mut. r?
-
由 Matthijs Hofstra 提交于
-
由 Matthijs Hofstra 提交于
-
由 Matthijs Hofstra 提交于
-
由 Graydon Hoare 提交于
-
- 02 4月, 2013 10 次提交
-
-
由 bors 提交于
Just some minor cleanup of version strings and copyrights.
-
由 bors 提交于
It seems nobody can figure out whether this is _supposed to_ make a difference anymore, and in testing it seems to work either way, so I removed it. One less alarming warning during a fresh build.
-
由 Graydon Hoare 提交于
-
由 bors 提交于
r? @brson
-
由 Tim Chevalier 提交于
-
由 bors 提交于
-
由 Brian Anderson 提交于
-
由 Brian Anderson 提交于
-
由 Graydon Hoare 提交于
-
由 Tim Chevalier 提交于
-
- 01 4月, 2013 13 次提交
-
-
由 bors 提交于
Turns out @ isn't valid for the ARM assembler.
-
由 Daniel Micay 提交于
-
由 bors 提交于
-
由 Brian Anderson 提交于
-
由 bors 提交于
Change fn() -> &fn().
-
由 Luqman Aden 提交于
Change fn() -> &fn().
-
由 bors 提交于
There's no reason to make them executable, and this throws a warning with the Arch Linux package lint tool (namcap) for .a files.
-
由 bors 提交于
Closes #5643
-
由 Daniel Micay 提交于
There's no reason to make them executable, and this throws a warning with the Arch Linux package lint tool (namcap) for .a files.
-
由 bors 提交于
Fix typo and add fixed length vec changes.
-
由 Daniel Micay 提交于
Closes #5643 This also removes the need to pass noexecstack to gcc, but that wasn't actually working anymore.
-
由 bors 提交于
-
由 Luqman Aden 提交于
Fix typo and add fixed length vec changes.
-
- 31 3月, 2013 11 次提交
-
-
由 Marvin Löbel 提交于
Added char_range_at_reverse underflow test
-
由 bors 提交于
Fixes #5423.
-
由 bors 提交于
#5405 Also, renames the confusingly named `use_new_rt` in `libcore/unstable/lang.rs`
-
由 Luqman Aden 提交于
-
由 Luqman Aden 提交于
-
由 bors 提交于
Closes #3549 The issue report has some reasoning, but I'd like to add that I don't think managed pointers belong in core. It's *possible* to write a safe doubly-linked list on top of `unsafe`, but it would be much more limited and I don't think there's much of a use case - it would lose a lot of flexibility. You're probably better off using a vector, hash table, tree, heap or ring buffer in almost every case.
-
由 Luqman Aden 提交于
-
由 Daniel Micay 提交于
Closes #3549
-
由 bors 提交于
-
由 bors 提交于
@nikomatsakis and I were talking about how the serializers were a bit too complicated. None of the users of With the `emit_option` and `read_option` functions, the serializers are now moving more high level. This patch series continues that trend. I've removed support for emitting specific string and vec types, and added support for emitting mapping types.
-
由 Daniel Micay 提交于
-