{"push_id":1387167456,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"9a3f5f20183bce73962a269a39c2d193c89e9743","before":"9e10da01c0078361b0b7518920afb4b58fd9a406","commits":[{"sha":"b97d68e1516d9a24c1ca4f77e80387acf3f75f1e","author":{"name":"Florian Hassanen","email":"df13a37ea702f0460dfe169fc6f0561a48854344@gmail.com"},"message":"eval macro form and inline its value","distinct":true,"url":"https://api.github.com/repos/h4ssi/pint/commits/b97d68e1516d9a24c1ca4f77e80387acf3f75f1e"},{"sha":"e1ca140bc9d71adeeb62cc17d10155f6f2d93d4d","author":{"name":"Florian Hassanen","email":"df13a37ea702f0460dfe169fc6f0561a48854344@gmail.com"},"message":"macro form always evals to its statically evaled value\n\nbut there is an important limitation:\n\ndue to the current design we need to track separate state\nwhen generating code and jitting code (because we have\nseparate modules for translating and jitting).\n\nthis could be unified in two ways, using llvm-orc (and\nuse the very same code that is used for executable output)\n\nor the other way round, use the modules used for jitting\nalso for output, but then output will consist of multiple\nmodules.\n\nthis state separation makes implementing macros more\ncomplicated than it need to be. for now they are\nimplemented with the limitation, that macro _definitions_\nmay only occur on the top level.","distinct":true,"url":"https://api.github.com/repos/h4ssi/pint/commits/e1ca140bc9d71adeeb62cc17d10155f6f2d93d4d"},{"sha":"9a3f5f20183bce73962a269a39c2d193c89e9743","author":{"name":"Florian Hassanen","email":"df13a37ea702f0460dfe169fc6f0561a48854344@gmail.com"},"message":"fix: display var name in error message","distinct":true,"url":"https://api.github.com/repos/h4ssi/pint/commits/9a3f5f20183bce73962a269a39c2d193c89e9743"}]}
{"actor":{"display_login":"h4ssi"}}