Jacob Lifshay

> > since this works: > > ```rust > > let a = 45; > > let b: u8 = a; > > ``` > > That works because integer...

> AFAIR original reason why `std::mem::forget` was deemed safe is because you can effectively omit drop by stuffing guard object into refcounted pointer loop. Object is alive but unreachable. >...

> > adding a method to `Utf8Error` that returns the valid prefix > > Is that backwards-compatible? To do this, `Utf8Error` would need to gain a lifetime parameter and the...

> * possibly recording metrics on when threads are started, although that would probably be most useful if there was some way to hook into thread destruction as well. TLS...

imho adding this for `HashMap` and `BTreeMap` with the generic value type implementing `Default` and `Extend` is what we should have...

> Hey _programmer jake_, had you meanwhile time to turn this issue into a real merge request? no, if I made a PR, I would have linked it here.

There could probably be a blanket impl which allows you to use `iter_of_results.try_collect()?`: ```rust impl TryFromIterator for S where S: TryFromIterator, E: From, { type Error = E; fn try_from_iter(iter:...

> What is the advantage of this when compared to the existing [`Iterator::try_collect`](https://doc.rust-lang.org/nightly/std/iter/trait.Iterator.html#method.try_collect)? I think the general idea is you can implement `TryFromIterator` for arrays, but not really using the...

one example of why it'd be nice to have collecting arrays from iterators -- when you want a chain of transforms applied to arrays and want functional syntax, but don't...

another example for something I've actually encountered: ```rust // simplified somewhat // a path `::my_crate::m::MyType` or `MyType` pub struct ParsedMyTypePath(syn::Path); // a parsed `MyType` pub struct ParsedMyType { pub my_type:...