| Age | Commit message (Collapse) | Author | Lines |
|---|
|
The new macro is available under the name ifmt! (only an intermediate name)
|
|
This is preparation for removing `@fn`.
This does *not* use default methods yet, because I don't know
whether they work. If they do, a forthcoming PR will use them.
This also changes the precedence of `as`.
|
|
Example:
if cfg!(test) {
calculation_to_run_only_when_testing();
}
Closes #8130.
|
|
The pipes compiler produced data types that encoded efficient and safe
bounded message passing protocols between two endpoints. It was also
capable of producing unbounded protocols.
It was useful research but was arguably done before its proper time.
I am removing it for the following reasons:
* In practice we used it only for producing the `oneshot` and `stream`
unbounded protocols and all communication in Rust use those.
* The interface between the proto! macro and the standard library
has a large surface area and was difficult to maintain through
language and library changes.
* It is now written in an old dialect of Rust and generates code
which would likely be considered non-idiomatic.
* Both the compiler and the runtime are difficult to understand,
and likewise the relationship between the generated code and
the library is hard to understand. Debugging is difficult.
* The new scheduler implements `stream` and `oneshot` by hand
in a way that will be significantly easier to maintain.
This shouldn't be taken as an indication that 'channel protocols'
for Rust are not worth pursuing again in the future.
|
|
keep/remove.
Example:
if cfg!(test) {
calculation_to_run_only_when_testing();
}
|
|
Fixes #7922.
Signed-off-by: OGINO Masanori <masanori.ogino@gmail.com>
|
|
|
|
I think of this as a stylistic opinion which shouldn't necessarily be enforced
by default on all users of rust, but that's just my opinion.
|
|
|
|
|
|
|
|
|
|
|
