-
Notifications
You must be signed in to change notification settings - Fork 157
Avoid register type aliases #466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
e272e10
to
55197b0
Compare
I'm a bit worried about generated source code size here. Do you have any numbers how much the source code blows up with that change? The compiler is already not too swift (yeah, sorry for the euphemism) thanks to the massive amount of generated code; we should try our best not to make it worse... |
Yes, code size and compilation time questions are opened. We can reduce code size using |
55197b0
to
d01cbe6
Compare
Rebased on master, leaving out the commits from #465 since the two PRs are completely independent. Please take another look. @therealprof I suspect your question is more geared towards #465 rather than here, but I'll answer it in both places. For
For
|
Oops, yes you're right. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
bors r+
Part 3 of #463, builds on #465.
Reg<REGISTER_SPEC>
. I think this helps clarify how the generated and generic types work together.No breaking change concerns on this change set.
r? @burrbull