Am 24.04.2013 04:36, schrieb Brian Anderson:
On 04/23/2013 03:24 PM, Marvin Löbel wrote:
Ever since fail and assert got turned into macros, failing with a
string message has become quite line-noisy:
fail!(~"cause")
Personally I think 3 is the easiest to implement option, and nice
even wit
On 04/23/2013 03:24 PM, Marvin Löbel wrote:
Ever since fail and assert got turned into macros, failing with a
string message has become quite line-noisy:
fail!(~"cause")
Personally I think 3 is the easiest to implement option, and nice even
without the fmt! optimisation. I already locally
> Con: Even harder to implement than 1, quite complex.
Hard to implement hardly seems like much of a con. This macro is going
to be used a lot, and making it nice seems like something that should
be done, even if it's a bit tricky to do.
jack.
___
Rust-
Ever since fail and assert got turned into macros, failing with a string
message has become quite line-noisy:
fail!(~"cause")
And including additional informations in the fail message makes the line
quite heavy, even though it should be encouraged for better failure
messages:
fail!(fmt!("fa