-
Notifications
You must be signed in to change notification settings - Fork 742
With replacements, we can generate a use of a type w/ no definition for that type #251
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
Comments
Hmmm.... somehow we end up with a field whose |
Ah nevermind, it's just our logging that was incomplete. Looks like it is being added as a builtin type:
|
This last point seems to be where we go wrong. We should be creating a named type for |
Note that the unresolved types change before processing both replacements Thanks for digging into this! :) On Nov 15, 2016 1:04 AM, "Nick Fitzgerald" [email protected] wrote:
|
This is actually fixed -- thanks @emilio :) |
creduce
ftw! \o/Flags:
--whitelist-type Rooted -- --std=c++14
Input:
Output:
Note how
MaybeWrapped
is used, but never defined. The<a>
tells me we are probably treating it as a named template argument.The text was updated successfully, but these errors were encountered: