Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRegression of the `typenum` crate on nightly #32637
Comments
This comment has been minimized.
This comment has been minimized.
|
triage: P-high |
rust-highfive
added
P-high
and removed
I-nominated
labels
Mar 31, 2016
This comment has been minimized.
This comment has been minimized.
|
|
pnkfelix
self-assigned this
Mar 31, 2016
This comment has been minimized.
This comment has been minimized.
|
Note that typenum PR #60 fixes the problem from the typenum side. |
This comment has been minimized.
This comment has been minimized.
|
@llogiq do you believe this to be a bug? |
This comment has been minimized.
This comment has been minimized.
|
Well, at best it's an unfortunate chain of events that unusual code may trigger, but that can be worked around. At worst, yes, it's a bug that can be worked around. If we deem it the latter, it's probably not too high on my wishlist. |
This comment has been minimized.
This comment has been minimized.
|
This particular instance of this problem seems to have resolved itself on
Looking over the git log for rust in range Closing as fixed. |
alexcrichton commentedMar 31, 2016
The typenum crate (as of paholg/typenum@10c15e3 at least) successfully compiles on stable/beta but fails to compile no nightly with the error message:
It this expected? Perhaps this was bumping "close to the recursion limit" beforehand? I haven't diagnosed this much, but at least the reproduction is easy!
cc @aturon (maybe specialization related)
cc @rust-lang/compiler