Eduardo Pinho

Could this be related to @shepmaster's recent changes in #306? To the best of my knowledge, SNAFU does not take advantage of `#[track_caller]` yet, and I imagine that there could...

I would advise that the error reporting constructs are made available without having to depend on Termination. This could exist either as a reporting function (like [this one](https://github.com/Enet4/dicom-rs/blob/master/dump/src/main.rs#L114-L137)) or as...

It's a bit early to require 1.61.0 to all SNAFU users, so it would have to be feature gated anyway, whereas viable alternatives to error reporting could be available now....

Is the [`std` feature flag](https://docs.rs/snafu/0.6.10/snafu/guide/feature_flags/index.html#std) disabled? ```toml [dependencies.snafu] version = "0.6.0" no-default-features = true features = ["rust_1_46"] ```

Well, I read this recent [blog post](http://creativcoder.me/post/checking_memory_leaks_in_rust_ffi/) on using Valgrind for this very purpose, and we are still advised to change the memory allocation system (using the nightly `alloc_system` feature)....

I would like to bump this issue, because not having an easy and simple way to programmatically retrieve a list of the project's grunt tasks (and _only_ the grunt tasks)...

Right now formatting support in RLS is behind the "unstable features" flags. Have you enabled this flag? See [here](https://github.com/rust-lang-nursery/rls#configuration) how to configure RLS in your project. It should be as...

I noticed that `parse_integers` might also have similar inconsistencies: The Julia version checks the outcome of `parse` only at the end of `t` iterations ([line 26](https://github.com/JuliaLang/Microbenchmarks/blob/master/perf.jl#L26), and [Lua too](https://github.com/JuliaLang/Microbenchmarks/blob/master/perf.lua#L66)), but...

> Rust seems like it would do well at this too You have caught my attention! The standard library already provides this as the iterator method [`max_by_key`](https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.max_by_key). So we have...

Here's [my Rust attempt](https://play.rust-lang.org/?gist=feba27b4bd244f394240b2ed111374ae&version=stable&mode=debug&edition=2015). This sure feels hard to optimize.