This website requires JavaScript.
Explore
Help
Sign In
OpenE2K
/
rust
Watch
2
Star
0
Fork
You've already forked rust
0
Code
Issues
Pull Requests
Projects
Releases
Wiki
Activity
e2k-1.52.0
rust
/
src
/
test
/
ui
/
attr-main-2.rs
12 lines
85 B
Rust
Raw
Permalink
Normal View
History
Unescape
Escape
tests: Add missing run-pass annotations
2019-07-26 23:54:25 +02:00
// run-pass
syntax: Feature gate #[start] and #[main] These two attributes are used to change the entry point into a Rust program, but for now they're being put behind feature gates until we have a chance to think about them a little more. The #[start] attribute specifically may have its signature changed. This is a breaking change to due the usage of these attributes generating errors by default now. If your crate is using these attributes, add this to your crate root: #![feature(start)] // if you're using the #[start] attribute #![feature(main)] // if you're using the #[main] attribute cc #20064
2015-01-16 19:55:24 +01:00
#![
feature(main)
]
xfail-fast the #[main] tests, r=burningtree
2013-01-19 02:44:26 +01:00
check-fast fallout from removing export, r=burningtree
2013-02-02 04:43:17 +01:00
pub
fn
main
(
)
{
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change]
2014-10-09 21:17:22 +02:00
panic!
(
)
allowing the entry point name to be something other than main add build tests
2013-01-11 10:08:01 +01:00
}
#[
main
]
fn
foo
(
)
{
}