about summary refs log tree commit diff
path: root/src/test/run-pass/yield.rs
AgeCommit message (Collapse)AuthorLines
2019-07-27tests: Move run-pass tests without naming conflicts to uiVadim Petrochenkov-21/+0
2019-07-27tests: Add missing run-pass annotationsVadim Petrochenkov-0/+2
2018-12-25Remove licensesMark Rousskov-10/+0
2018-09-21Allow various lints as part of ui-ifying `src/test/run-pass` suite.Felix S. Klock II-0/+2
2016-02-11Ignore tests that use threads on emscriptenPierre Krieger-0/+2
2015-02-17Fallout from stabilizationAaron Turon-5/+5
2015-01-06Fallout from stabilizationAaron Turon-1/+1
2014-12-18Revise std::thread API to join by defaultAaron Turon-6/+6
This commit is part of a series that introduces a `std::thread` API to replace `std::task`. In the new API, `spawn` returns a `JoinGuard`, which by default will join the spawned thread when dropped. It can also be used to join explicitly at any time, returning the thread's result. Alternatively, the spawned thread can be explicitly detached (so no join takes place). As part of this change, Rust processes now terminate when the main thread exits, even if other detached threads are still running, moving Rust closer to standard threading models. This new behavior may break code that was relying on the previously implicit join-all. In addition to the above, the new thread API also offers some built-in support for building blocking abstractions in user space; see the module doc for details. Closes #18000 [breaking-change]
2014-06-18Fallout from TaskBuilder changesAaron Turon-5/+2
This commit brings code downstream of libstd up to date with the new TaskBuilder API.
2014-04-23Move task::task() to TaskBuilder::new()Steven Fackler-1/+2
The constructor for `TaskBuilder` is being changed to an associated function called `new` for consistency with the rest of the standard library. Closes #13666 [breaking-change]
2014-03-15log: Introduce liblog, the old std::loggingAlex Crichton-4/+4
This commit moves all logging out of the standard library into an external crate. This crate is the new crate which is responsible for all logging macros and logging implementation. A few reasons for this change are: * The crate map has always been a bit of a code smell among rust programs. It has difficulty being loaded on almost all platforms, and it's used almost exclusively for logging and only logging. Removing the crate map is one of the end goals of this movement. * The compiler has a fair bit of special support for logging. It has the __log_level() expression as well as generating a global word per module specifying the log level. This is unfairly favoring the built-in logging system, and is much better done purely in libraries instead of the compiler itself. * Initialization of logging is much easier to do if there is no reliance on a magical crate map being available to set module log levels. * If the logging library can be written outside of the standard library, there's no reason that it shouldn't be. It's likely that we're not going to build the highest quality logging library of all time, so third-party libraries should be able to provide just as high-quality logging systems as the default one provided in the rust distribution. With a migration such as this, the change does not come for free. There are some subtle changes in the behavior of liblog vs the previous logging macros: * The core change of this migration is that there is no longer a physical log-level per module. This concept is still emulated (it is quite useful), but there is now only a global log level, not a local one. This global log level is a reflection of the maximum of all log levels specified. The previously generated logging code looked like: if specified_level <= __module_log_level() { println!(...) } The newly generated code looks like: if specified_level <= ::log::LOG_LEVEL { if ::log::module_enabled(module_path!()) { println!(...) } } Notably, the first layer of checking is still intended to be "super fast" in that it's just a load of a global word and a compare. The second layer of checking is executed to determine if the current module does indeed have logging turned on. This means that if any module has a debug log level turned on, all modules with debug log levels get a little bit slower (they all do more expensive dynamic checks to determine if they're turned on or not). Semantically, this migration brings no change in this respect, but runtime-wise, this will have a perf impact on some code. * A `RUST_LOG=::help` directive will no longer print out a list of all modules that can be logged. This is because the crate map will no longer specify the log levels of all modules, so the list of modules is not known. Additionally, warnings can no longer be provided if a malformed logging directive was supplied. The new "hello world" for logging looks like: #[phase(syntax, link)] extern crate log; fn main() { debug!("Hello, world!"); }
2013-12-16Fallout of rewriting std::commAlex Crichton-1/+1
2013-10-25Remove ancient emacs mode lines from test casesBrian Anderson-1/+0
These are relics that serve no purpose.
2013-10-22Drop the '2' suffix from logging macrosAlex Crichton-4/+4
Who doesn't like a massive renaming?
2013-10-18Made `std::task::TaskBuilder::future_result()` easier to useMarvin Löbel-3/+2
2013-09-30rpass: Remove usage of fmt!Alex Crichton-4/+4
2013-08-16Reserve 'yield' keywordKevin Ballard-3/+3
Rename task::yield() to task::deschedule(). Fixes #8494.
2013-05-29librustc: Stop reexporting the standard modules from prelude.Patrick Walton-0/+2
2013-05-08test: Fix tests.Patrick Walton-1/+1
2013-05-08test: Fix tests and the pipe compilerPatrick Walton-1/+3
2013-03-26option: rm functions that duplicate methodsDaniel Micay-1/+1
2013-02-15tests/tutorials: Get rid of `move`.Luqman Aden-2/+2
2013-02-01check-fast fallout from removing export, r=burningtreeGraydon Hoare-1/+1
2012-12-13librustc: Make `use` statements crate-relative by default. r=brsonPatrick Walton-6/+3
2012-12-10Reliciense makefiles and testsuite. Yup.Graydon Hoare-0/+10
2012-10-23core: Use PortOne instead of Future in future_resultBrian Anderson-1/+1
2012-10-12Make moves explicit in rpass testsTim Chevalier-2/+2
2012-09-11Convert 'use' to 'extern mod'. Remove old 'use' syntaxBrian Anderson-1/+1
2012-09-05test: "import" -> "use"Patrick Walton-2/+1
2012-08-26Camel case the option typeBrian Anderson-2/+2
2012-08-23`m1!{...}` -> `m1!(...)`Paul Stansifer-4/+4
2012-08-14fix fallout from future de-mode-ing.Graydon Hoare-1/+1
2012-08-07Change task().future_result's argument modeBen Blum-1/+1
2012-07-30Change syntax extension syntax: `#m[...]` -> `m!{...}`.Paul Stansifer-4/+4
2012-07-23Convert bench and run-pass tests to new task_builder interfaceBen Blum-4/+3
2012-07-01Convert to new closure syntaxBrian Anderson-1/+1
2012-06-30Eliminate usages of old sugared call syntaxBrian Anderson-1/+1
2012-04-05Rename task::task_builder to task::builderTim Chevalier-1/+1
Closes #2120.
2012-03-13Overhaul constructor naming in libsBrian Anderson-1/+1
2012-02-20core: New task APIBrian Anderson-2/+4
2012-01-06port over the tests to use the new APINiko Matsakis-2/+2
2011-12-22Register snapshots and switch logging over to use of log_full or #error / ↵Graydon Hoare-4/+4
#debug.
2011-12-13Copy first batch of material from libstd to libcore.Graydon Hoare-2/+2
2011-10-20Remove temporary fn# syntaxBrian Anderson-1/+1
2011-10-20Drop the 2 from the spawn*2 functionsBrian Anderson-1/+1
Issue #1022
2011-10-20Convert tests to use bare-fn spawnBrian Anderson-3/+4
Issue #1022
2011-08-25Cleaning up task and comm exports, updating all the test cases.Eric Holk-2/+2
2011-08-20ReformatBrian Anderson-1/+1
This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-08-17Using move-mode for spawn thunks to avoid race conditions.Eric Holk-1/+2
2011-08-15Porting a bunch of tests over.Eric Holk-2/+3