ticki
ticki
Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
@jimmycuadra I agree. Functions should be small and compact, however sometimes you want to be able to know the argument order without looking up the signature (which keyword arguments solve),...
Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
@petrochenkov The problem you outline is a problem with macros, not a need for method variadicity.
Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
> No, using structs instead of named arguments is a bad thing. Not true. Structs are strongly typed (hence less prone to errors) and makes it possible to efficiently reuse...
Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
> If your functions often take fixed number of arguments, all other users should obey? I'm just saying that introducing syntactic sugar for such a small special case is not...
Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
@KalitaAlexey I'm not exactly sure what you're asking, but I supose you mean "Is it mandatory to provide the name of the parameters to the function, if we get keyword...
I really, really like this proposal. I had some cases where I could choose to either rewrite the same piece of code a lot of times (because it's borrowing self)...
:+1: Always bothered me.
> What backtrace information? We use the symbol names or debug info, just like C and C++. > If you're compiling an executable in release mode, all you have to...
> To compile without debug info: remove -g. Cargo.toml has a way to turn it off even for debug mode, while release mode doesn't come with debug info. That'll still...
> Panics are not "backtrace information", they're file!() and line!() macros - having a way to obscure those would be useful, but you'd have to recompile the entire libstd in...