-
Notifications
You must be signed in to change notification settings - Fork 427
Conversation
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.
The failing test needs to be addressed.
@@ -150,6 +141,15 @@ export function build(name: string, realm: Realm, inheritError?: boolean = true) | |||
message.throwIfNotConcrete(); | |||
} | |||
|
|||
// Build a text description of the stack. | |||
let stackDesc = { | |||
value: buildStack(realm, O), |
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.
buildStack does not yet handle abstract messages. You can add such support by emitting the stack as a string template. Alternatively, you could just comment out the throw with a TODO comment, along with an issue describing what needs to be done.
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.
👍
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.
You still need to fix a Flow error, but other than that it looks good to me.
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.
@calebmer is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Because of an ordering bug messages weren’t being added to the error stacks thrown by Prepack. This made debugging runtime issues in generated Prepack code difficult.
Input
Output Before
Output After