Skip to content

Conversation

@jamesr66a
Copy link
Collaborator

@jamesr66a jamesr66a commented Jun 15, 2019

Stack from ghstack:

I realized two things:

  1. There's an unnecessary ErrorReport if a NamedTuple constructor is called with kwargs. Removed it
  2. We don't actually support the default values for fields, so we now throw an error if a NamedTuple definition has them.

Differential Revision: D15860005

@pytorchbot pytorchbot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Jun 15, 2019
[JIT] Some small fixes for NamedTuple

gh-metadata: pytorch pytorch 21813 gh/jamesr66a/2/head
[JIT] Some small fixes for NamedTuple

gh-metadata: pytorch pytorch 21813 gh/jamesr66a/2/head
Copy link
Contributor

@zdevito zdevito left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3.6 roentgen. not great. not terrible. should be good to go once it doesn't catch std::exception.

James Reed added 3 commits June 17, 2019 10:49
[JIT] Some small fixes for NamedTuple

gh-metadata: pytorch pytorch 21813 gh/jamesr66a/2/head
[JIT] Some small fixes for NamedTuple

gh-metadata: pytorch pytorch 21813 gh/jamesr66a/2/head
[JIT] Some small fixes for NamedTuple

gh-metadata: pytorch pytorch 21813 gh/jamesr66a/2/head
@facebook-github-bot
Copy link
Contributor

@jamesr66a merged this pull request in 74104f3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Merged oncall: jit Add this issue/PR to JIT oncall triage queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants