> I'd get the inscrutable "Could not Instantiate T" with no other context to > indicate WHY instantiation wasn't possible.
This is why I think improving error messages should be a bigger priority for Nim. > Another example of that one; I recently had need to use object storage. > There's one fairly complete Nim library that covers a lot of AWS's services > (I didn't look for other cloud providers). But, unfortunately, it makes it > VERY hard to figure out how to use it. Then there are a few really basic ones > that only do object storage, and aren't always even well written. I took the > easy path for now, but I was thinking, there are good C libraries here; NIM > would do well to have a strong, well-documented library, even if it wraps > under the hood. Especially if it can abstract across multiple providers > reasonably well. I'd prefer to not have integration with proprietary commercial software as part of the standard library. (And it's Nim, not NIM.)
