Wrapping anyhow::Error in another error loses backtrace

[Ten16]

Migrating from failure to anyhow, I encounter an issue where I start losing backtraces when anyhow::Errors are wrapped in another error type:

#[test]
fn backtrace_preserved_after_thiserror_derive() {
	#[derive(Debug, thiserror::Error)]
	pub enum SomeError {
		#[error(transparent)]
		Anyhow(anyhow::Error),
	}

	let mut errs = (0..2).map(|_| anyhow::anyhow!("aaa"));

	let wrapped = anyhow::Error::from(SomeError::Anyhow(errs.next().unwrap()));
	let notwrapped = errs.next().unwrap();

	assert_eq!(wrapped.backtrace().to_string(), notwrapped.backtrace().to_string());
}

It is a kind of usage suggested by the documentation:

thiserror/src/lib.rs

Lines 194 to 195 in 799b3d3

	//! #[error(transparent)]
	//! Other(#[from] anyhow::Error), // source and Display delegate to anyhow::Error

It used to be possible to work around this issue in failure (even on stable, which we are on).
It would seem fine if the backtrace could only be propagated if coming from anyhow.

Is it possible to achieve something like this with the anyhow/thiserror combination?