2 ms·
> and for every new one there have been painful migrations for codebases of any significant size Why did you migrate though? At work, we're still using error_c
by littlestymaar 4y ago
> and for every new one there have been painful migrations for codebases of any significant size
Why did you migrate though? At work, we're still using error_chain for the oldest library we have since the ergonomics of the library isn't an issue for these stable-ish libs. If what you already have works, just don't migrate. It's not like there's likely hidden segfaults or memory vulns waiting there…
- kelnos 4y ago> It's not like there's likely hidden segfaults or memory vulns waiting there… It's funny you mention that, because the now-deprecated 'failure' crate has such a memory-safety vulnerability: https://github.com/rust-lang-deprecated/failure/issues/336 https://github.com/rust-lang-deprecated/failure/issues/336 Granted, consuming code is only vulnerable if they opt-in to implementing a provided trait method that most people should never ever need to implement. But I would still try to eliminate 'failure' from my dependency graph if possible (and I recently submitted PRs to two dependencies I was using to remove 'failure' from their dependencies).