Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
alfiedotwtf
on March 3, 2017
|
parent
|
context
|
favorite
| on:
Rust's language ergonomics initiative
Also that was just an example. Another along the same line:
x = 42 if y > 7;
Rather than
x = match y > 7 { true => 42, false => 0 };
Or even:
foo() if bar();
Rather than:
if bar() { foo() }
kibwen
on March 3, 2017
[–]
Given how crucially important scopes are to Rust, this would be a uniquely poor fit. :P
alfiedotwtf
on March 3, 2017
|
parent
[–]
Yeah, I totally understand why not. Just my comments from the peanut gallery :)
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: