{"action":"created","issue":{"url":"https://api.github.com/repos/rust-lang/rfcs/issues/1071","labels_url":"https://api.github.com/repos/rust-lang/rfcs/issues/1071/labels{/name}","comments_url":"https://api.github.com/repos/rust-lang/rfcs/issues/1071/comments","events_url":"https://api.github.com/repos/rust-lang/rfcs/issues/1071/events","html_url":"https://github.com/rust-lang/rfcs/issues/1071","id":69359214,"number":1071,"title":"Should const-evaluation be dynamically-typed or statically-typed?  (And with what types?)","user":{"login":"pnkfelix","id":173127,"avatar_url":"https://avatars.githubusercontent.com/u/173127?v=3","gravatar_id":"","url":"https://api.github.com/users/pnkfelix","html_url":"https://github.com/pnkfelix","followers_url":"https://api.github.com/users/pnkfelix/followers","following_url":"https://api.github.com/users/pnkfelix/following{/other_user}","gists_url":"https://api.github.com/users/pnkfelix/gists{/gist_id}","starred_url":"https://api.github.com/users/pnkfelix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pnkfelix/subscriptions","organizations_url":"https://api.github.com/users/pnkfelix/orgs","repos_url":"https://api.github.com/users/pnkfelix/repos","events_url":"https://api.github.com/users/pnkfelix/events{/privacy}","received_events_url":"https://api.github.com/users/pnkfelix/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-18T23:21:34Z","updated_at":"2015-04-18T23:22:14Z","closed_at":null,"body":"Currently our handling of types in const-evaluation is pretty ad-hoc.\r\n\r\nSee for example: https://github.com/rust-lang/rust/issues/23833 or more generally sevefral on the list at https://github.com/rust-lang/rust/issues/23897\r\n\r\nThe const-evaluator often tries to act like it can figure out an expected type from the context and pass it in, but this is not always possible in general.\r\n\r\nAnd in any case, it may make more sense to have the const-evaluated values carry around the actual computed types.  But then this leads to issues like: Should the computed types be so strict as to be \"this is the value `-3` of type `i8`\"?  Or would it be better to be more flexible and have the computed type just be \"this is the value `-3` of type `signed integer`, so that it could be used with any signed integer type that can hold that value?"},"comment":{"url":"https://api.github.com/repos/rust-lang/rfcs/issues/comments/94212805","html_url":"https://github.com/rust-lang/rfcs/issues/1071#issuecomment-94212805","issue_url":"https://api.github.com/repos/rust-lang/rfcs/issues/1071","id":94212805,"user":{"login":"pnkfelix","id":173127,"avatar_url":"https://avatars.githubusercontent.com/u/173127?v=3","gravatar_id":"","url":"https://api.github.com/users/pnkfelix","html_url":"https://github.com/pnkfelix","followers_url":"https://api.github.com/users/pnkfelix/followers","following_url":"https://api.github.com/users/pnkfelix/following{/other_user}","gists_url":"https://api.github.com/users/pnkfelix/gists{/gist_id}","starred_url":"https://api.github.com/users/pnkfelix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pnkfelix/subscriptions","organizations_url":"https://api.github.com/users/pnkfelix/orgs","repos_url":"https://api.github.com/users/pnkfelix/repos","events_url":"https://api.github.com/users/pnkfelix/events{/privacy}","received_events_url":"https://api.github.com/users/pnkfelix/received_events","type":"User","site_admin":false},"created_at":"2015-04-18T23:22:14Z","updated_at":"2015-04-18T23:22:14Z","body":"(I consider https://github.com/rust-lang/rust/issues/15270 to be an instance of this, so I am not planning to clone that issue.)"}}