hey folks!
in the function declaration
fn foo() {}
and
fn bar() -> ! {}
why is the latter used?
I believe it's means it will return error
Like
Nothing in Scala
is there a way to check it?
im so new to rust
I can try to help/send docks when I will be at my PC
this subreddit says ! indicates that the function never returns
Yeah, like panic! which is error
My sentence about
return error is quite wrong
for instance you can use it when you want to call a function which will exit the application
or call a function which
should and will panic etc...
ah
thanks
Welcome :thumbsup:
Hi, I used vector in C++ STL and rust. And felt rust has many features using vector than C++. How come these possible, why not C++ STL doesn't implement those.. ?
I understand it's a design constraint.
I think partially it's about who makes standards. In C++ there is committed for that purpose. In rust the community can be part of any rfc/design making, and it's makes rust amazing as it is
Not familiar with C++, what features does
Vec have that std::vector doesn't?
At least map, flatmap, operations with lambdas etc ...
Even though if I correct C++ has lambdas
I mean C++ 11
You can find those operations in boost and not in the std
Is it available for rust ? Any stable UI framework in rust ?
@Jeshwanth maybe this does the trick for you ? https://github.com/PistonDevelopers/conrod
As an UI framework (its more an lib but meh.)
Is it possible to bring all the struct fields of a variable into scope?
ie.
let c = Foo { x: 1 };
use c::*;
Thanks @HeapUnderfl0w I will have a look
@dwijnand You could do:
let Foo { x } = c;If Foo has other fields, but you want to bring only x in scope, you can do:
let Foo { x, .. } = c;
Is there syntax to introduce all the fields?
ala
let Foo { * } = c;
Why do you need that?
You'll need exact variable names anyway
Doesn't look like it, no. https://is.gd/5GGo4I
I guess it's a matter of explicit over implicit.
Ok. Well 1 decontructing for all fields, explicitly, still beats 1-per-field. Thank you.
@vitvakatu Just to remove the maintaince. As I add fields to Foo and use them I don't need to declare them explicitly.
It's awful syntax if you have smth like:
struct Foo { x: i32 }
let c = Foo { x: 30 };
... multiple lines of code ...
let x = ...
... multiple lines of code ...
let Foo { * } = c;
Hi! Does anyone want to to check if this was reported? ICE on nightly in
https://is.gd/rOP5eK
impl Trait definitionhttps://is.gd/rOP5eK
@samoylovfp Looks like this one: rust-lang/rust#43073