Mazdak Farrokhzad
Mazdak Farrokhzad
@Boscop That's fine; You can do it for non-pub items then. However, you could potentially hold the type abstract in the crate and so it could work again.
@dignifiedquire I'd just write a PR against https://github.com/rust-lang/rust/ and then T-libs can decide what to do.
Instead of @arantius solution you could pass in the parent as root but but attach it directly. You should rarely ever use null as root in a call to inflate....
Yep; @jonas-schievink is correct. Rust does not support what is referred to in Haskell as [ScopedTypeVariables](https://www.microsoft.com/en-us/research/publication/lexically-scoped-type-variables/). Moreover, even if you could use the type parameter `T`, calling `T::default()` would fail...
> From #48427, the same behavior is seen for `static`s @estebank It's the same for all nested items really; STV is the solution to all of them except for maybe...
cc @nikomatsakis
With respect to the surface syntax for VLAs, I'm *highly* (to put it mildly) skeptical of permitting `[T; n]` because: + the risk of introducing accidental VLAs is too high...
Yea -- tho if we say that it is "unspecified behavior" (for the parts which it isn't well defined as in e.g. `transparent`) we'll need to impress upon people that...
Sorry for not responding or merging this one earlier, ill take a look at the changes tonight. You can close this one and update all at once if you want,...
I thought you meant to fix the jcenter thing and then make a PR for that + this PR, so that it becomes a new PR. If you want to...