Does this library allocate?

[lilith]

I'm wondering if this is suitable for representing errors in a potential out-of-memory condition (i.e. malloc failure)?

[brson]

Yes, this library allocates in the chain_err method. Putting the "chained errors" into boxes on the heap is one of the primary tradeoffs it makes.

[lilith]

Would there be any way to create or mark an error to prevent allocations? I.e, if I'm manually handling OOM conditions, but want to represent the result as an Error, can I do so without allocs?

Clarification: I wouldn't expect any behavior other than a generic error with no metadata; I would also expect chain_error to discard anything provided.

[Yamakaky]

Closing for #64

[lilith]

My use case is runtime-based, i.e, I'd like chain_error functionality except for one class of origin error. I think the compile-time feature is awesome, though.

I should probably private-fork error_chain given the particular requirements of my lib and try to figure out a way to make this work. Thanks for the feedback!

[Yamakaky]

It could help others. Do you have any idea how we should change the syntax?

[lilith]

I haven't done any exploratory work, no. I'm a few days off from refactoring error handling in my lib.